Systems and methods for providing balance and event notifications

ABSTRACT

The disclosed embodiments include methods and systems for providing account and event status notifications. The disclosed embodiments include, for example, a device including a memory storing software instructions and one or more processors configured to execute the software instructions to perform operations. In one aspect, the operations may include obtaining information identifying an event and a deadline specified by a user. The obtained information may link the event and deadline to corresponding user-specified temporal intervals. The operations may also include determining whether a current date falls within a time period prior to the deadline, the time period being established by the first temporal interval. When the current date falls within the time period, the operations may generate first notification information that, when presented via a client device in accordance with a user-specified indicator type, notified the user that the current sate falls within the first time period.

CROSS-REFERENCE TO RELATED APPLICATION

This application is a continuation-in-part of U.S. patent applicationSer. No. 14/585,069, filed Dec. 29, 2014, which claims the benefit ofpriority to U.S. Provisional Patent Application No. 61/923,355, filedJan. 3, 2014, the entire disclosure of which are expressly incorporatedherein by reference to their entireties

BACKGROUND

1. Technical Field

The present disclosure generally relates to systems and methods forportraying information, and more particularly, and without limitation,to systems and methods for providing notifications for accounts.

2. Background

Status notifications provide users with information that may be helpfulin assessing current situations relating to monitored items. In thefinancial service industry, for example, users benefit from systems thatprovide updates to the status of certain account parameters. Suchmechanisms, however, are cumbersome for users and may require multipleoperations to view the notification, such as logging in to an onlinebanking site, opening an application to review notifications, and thelike.

Aspects of the disclosed embodiments provide user-friendly visual,audial, or haptic (tactile) indicators that relay the status of one ormore items in an accurate and efficient manner.

SUMMARY

The disclosed embodiments include methods and systems or providingaccount status notifications.

The disclosed embodiments include, for example, an apparatus having astorage device and at least one processor coupled to the storage device.The storage device may store instructions for controlling the at leastone processor when executed by the at least one processor. The at leastone processor may be operative with the instructions and configured toobtain information identifying an event and corresponding deadlinespecified by a user. In some aspects, the information may link the eventand deadline to a plurality of temporal notification intervals, and thetemporal notification intervals may be linked to corresponding indicatortypes. The at least one processor may be further configured to determinewhether a current date falls within a first time period prior to thedeadline. The first time period may be established by a first one of thetemporal notification intervals. When the current date is determined tofall within the first time period, the at least one processor may befurther configured to identify a first indicator type associated withthe first temporal notification interval. The at least one processor maybe further configured to generate first notification information for theidentified event based on at least one notification rule and a status ofthe identified event. In one aspect, the identified event status beingindicative of the disposition of the current date within the first timeperiod. The at least one processor may be further configured to providethe first notification information to a device associated with the user.In additional aspects, the first notification information may instructthe user device to generate and present, to the user, a first eventstatus indicator having at least one of a visual, audible, or tactilecharacteristic consistent with the at least one notification rule andthe first indicator type.

The disclosed embodiments also include a computer-implemented methodthat obtains, by at least one processor, information identifying anevent and corresponding deadline specified by a user. In some aspects,the information may link the event and deadline to a plurality oftemporal notification intervals, and the temporal notification intervalsmay be linked to corresponding indicator types. The method includesdetermining, by the least one processor, whether a current date fallswithin a first time period prior to the deadline. The first time periodmay be established by a first one of the temporal notificationintervals. When the current date is determined to fall within the firsttime period, the method may identify, by the least one processor, afirst indicator type associated with the first temporal notificationinterval, and generate, by the least one processor, first notificationinformation for the identified event based on at least one notificationrule and a status of the identified event. In one aspect, the identifiedevent status may be indicative of the disposition of the current datewithin the first time period. The method may also provide, by the leastone processor, the first notification information to a device associatedwith the user. In additional aspects, the first notification informationmay instruct the user device to generate and present, to the user, afirst event status indicator having at least one of a visual, audible,or tactile characteristic consistent with the at least one notificationrule and the first indicator type.

In other embodiments, a device may include a storage device and at leastone processor coupled to the storage device. The storage device maystore software instructions for controlling the at least one processorwhen executed by the at least one processor. In an embodiment, the atleast one processor may be operative with the software instructions andmay be configured to receive status notification information for atleast one event. In one aspect, the event may be associated with acorresponding deadline, and the received status notification informationmay reflect a disposition of a current date within a first time periodprior to the deadline. In additional aspects, the first time period maybe established by the first temporal interval, and the first temporalinterval may be associated with a first indicator type. Based on thereceived status notification information, the at least one processor maybe further configured to generate an event status indicator inaccordance with the first indicator type. The generated event statusindicator may reflect the disposition of the current date within thefirst time period. The at least one processor may be further configuredto present, to the user, the event status indicator without receivinginput from the user. In certain aspects, at least one a visual, audible,or tactile characteristic of the presented event status indicator may beconsistent with first indicator type.

The accompanying drawings constitute a part of this specification. Thedrawings illustrate several embodiments of the present disclosure and,together with the description, serve to explain the principles of thedisclosed embodiments as set forth in the accompanying claims.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 depicts an exemplary computing environment consistent withdisclosed embodiments.

FIG. 2 depicts an exemplary computing system consistent with thedisclosed embodiments.

FIGS. 3A, 3B, 3C, and 3D depict flowcharts of an exemplary process forproviding a balance notification indicator consistent with disclosedembodiments.

FIG. 4 depicts an exemplary client device portraying a pictorial balanceindicator consistent with disclosed embodiments.

FIGS. 5A, 5B, 5C, 5D, 5E, 5F, 5G, and 5H depict exemplary pictorialbalance indicators consistent with disclosed embodiments.

FIG. 6 depicts an exemplary transaction account and indicatorenvironment consistent with disclosed embodiments.

FIG. 7 depicts an exemplary transaction account and indicatorenvironment for a single user associated with multiple accountsconsistent with disclosed embodiments.

FIGS. 8A, 8B, 9A, 9B, and 9C depict exemplary account status indicatorspresented within a user's field-of-view, consistent with the disclosedembodiments.

FIG. 10 illustrates an exemplary data structure for storing connecteddevice data, consistent with the disclosed embodiments.

FIG. 11 is a flow chart of an exemplary process for providing accountstatus notifications to eligible connected devices, consistent withdisclosed embodiments.

FIG. 12 is a flow chart of an exemplary process for generated andproviding event notification information to networked devices.

DESCRIPTION OF THE EMBODIMENTS

Reference will now be made in detail to embodiments, examples of whichare illustrated in the accompanying drawings. Wherever possible, thesame reference numbers will be used throughout the drawings to refer tothe same or like parts.

In this application, the use of the singular includes the plural unlessspecifically stated otherwise. In this application, the use of “or”means “and/or” unless stated otherwise. Furthermore, the use of the term“including,” as well as other forms such as “includes” and “included,”is not limiting. In addition, terms such as “element” or “component”encompass both elements and components comprising one unit, and elementsand components that comprise more than one subunit, unless specificallystated otherwise.

FIG. 1 illustrates an exemplary computing environment consistent withcertain disclosed embodiments. In one aspect, computing environment 100may include a client device 104, system 140, and communications network120 connecting one or more of the components of environment 100.

In one embodiment, system 140 may include one or more computer systemsconfigured to gather, process, and store information. System 140 may befurther configured to execute software instructions stored in memoryperforming one or more processes consistent with the disclosedembodiments. In certain aspects, system 140 may be associated withbusiness entity 160, although such association is not required. In oneembodiment, business entity 160 may be any type of entity (e.g.,business, service provider, etc.) that may provide and maintain one ormore accounts for one or more users (e.g., user 110). For example,business entity 160 may include, for example, a financial institution,retail store, university, merchant, online retail service provider,restaurant, hotel, or the like. In some embodiments, business entity 160may be a commercial bank, investment bank, a provider of a paymentinstrument or financial service accounts, etc. As an example, afinancial service account may be a checking, savings, credit, debit,gift card, reward, trading, investment, and/or loyalty account. In someaspects, a payment instrument may include, but is not limited to, apersonal or corporate credit card, debit card, prepaid credit or debitcard, gift card, or check instrument. In certain embodiments, an accountmay be used in a transaction, such as a purchase transaction, a bankingtransaction, or other forms of financial service transactions.

While the present disclosure sometimes describes certain aspects ofbusiness entity 160 as a financial institution, the disclosedembodiments are not so limited. In other embodiments, system 140 may beassociated with a business entity 160 providing accounts for users 110associated with other types of transactions, such as online services(e.g., an online retailer), merchant related services (e.g., purchasinggoods or services at a physical retailer or restaurant, etc.),educational institution related services (e.g., student meal plans,etc.), and the like. Moreover, aspects of the disclosed embodiments arenot limited to financial service accounts. In certain embodiments, anaccount may be associated with one or more account parameters, such asaccount balance, account limit, usage limit, remaining usage credit, orother parameters. The disclosed embodiments may be configured todetermine, access, or generate information associated with one or moreaccount parameters relating to one or more accounts for one or moreusers (e.g., user 110).

In one embodiment, system 140 may include one or more servers 142 andone or more memories, such as data repository 144. In one embodiment,server 142 may include a front end 142A, and a back end 142B incommunication with front end 142A, although the configuration of server142 is not limited to such configurations. In one example, front end142A and back end 142B of server 142 may be incorporated into a singlecomputer, or any additional or alternate computing device apparent toone or skill in the art. In other embodiments, front end 142A andbackend 142B may be distributed computing elements. In certain aspects,front end 142A may be one or more software programs, such as a softwareapplication (e.g., a web service) executed by one or more processorsincluded in server 142. Similarly, backend 142B may be one or moresoftware programs executed by one or more processors included in server142. Server 142 is not limited to such configurations. In additionalembodiments, front end 142A software can be executed by a server orcomputing system separate from a server or computing system thatexecutes back end 142B. In other embodiments, server 140 may beconfigured without front end 142A and/or back end 142B.

Server 142 may be configured to execute software instructions to performone or more processes consistent with the disclosed embodiments. Server142 may be implemented with one or more processors or computer-basedsystems. In one embodiment, client device 104 may exchange informationand parameters facilitating execution of one or more transactionsassociated with system 140 as described herein.

Data repository 144 may be one or more data storages configured to storeinformation consistent with the disclosed embodiments. In one aspect,data repository 144 may include customer data 144A, account data 144B,and transaction data 144C. In one aspect, customer data 144A may includeone or more data records uniquely identifying one or more users 110 ofbusiness entity 160 associated with system 140. By way of example, acustomer of a financial institution (e.g., business entity 160) mayaccess a web page associated with system 140 (e.g., through a web serverexecuted by front end 142A), and subsequently register for onlinebanking services and provide data. The data may be linked to thecustomer and stored within customer data 144A.

In certain aspects, customer data 144A may include personal informationassociated with a user 110 (e.g., a name, home address, or date ofbirth). Customer data 144A may also include one or more authenticationcredentials associated with registered customers of the issuing bank.For example, the authentication credentials may include, but are notlimited to, a user name, a user-specified password, a system-generatedpassword, or an alphanumeric identification number (e.g., a PIN number)specified by the user or assigned by system 140. Other types of customerinformation may be stored and used by the disclosed embodiments.

Additionally or alternatively, customer data 144A may includeinformation facilitating enhanced authentication techniques. Forexample, customer data 144A may store information identifying a securityquestion associated with a customer (e.g., “What is your mother's maidenname?”) and the customer's registered answer to the security question.Customer data 144A may also include information identifying a particularsecurity image or avatar selected by the user and displayed by the userduring the authentication process.

Customer data 144A may include client device identification informationidentifying one or more client devices 104 registered to user 110. Inone embodiment, the user may provide the client device identificationinformation (e.g., a mobile telephone number provided by the user whenregistering for online banking services, a mobile access control (MAC)address associated with client device 104, etc.). Alternatively, server142 may be configured to execute processes that automatically collectclient device identification information (e.g., collecting an InternetProtocol (IP) address associated with the customer's smartphone).

In an embodiment, customer data 144A may include geographic positiondata associated with user 110 and/or at least one of client devices 104registered to user 110. For instance, the geographic position data mayidentify a current geographic position of user 110 and/or client devices104, and additionally or alternatively, one or more prior geographicpositions of user 110 and/or client devices 104. Geographic positiondata consistent with the disclosed embodiments may include, but is notlimited to, a latitude, longitude, and/or altitude of a current or priorgeographic position, additional geospatial coordinates or positioninformation (e.g., a Where On Earth Identified (WOEID)), a geographicregion associated with a current or prior geographic position, and/or apostal code associated with a current or prior geographic position.

In certain aspects, system 140 may obtain a portion of the geographicposition data from client device 104 across communications network 120.By way of example, client device 104 may include a global positionsystem (e.g., a GPS) that tracks a current geographic position of clientdevice 104, and client device 104 may transmit geographic position dataindicative of the current geographic position of client device 104 tosystem 140 across communication network 120. For instance, client device104 may append the geographic position data to data transmitted tosystem 140 in response to a completed transaction, and/or a requiredupdate to system 140. In other instances, client device 104 may transmitthe geographic position data to a third-party system (e.g., a mobiletelecommunications provider), and system 140 may obtain portions of thegeographic position data from the third-party system across network 140through an appropriate application programming interface (API). Uponreceipt of the geographic position data from client device 104 and/orthe third party system, system 140 may be configured to format and storethe received positional information within database 144 (e.g., asportions of customer data 144A).

In certain aspects, account data 144B may include account informationidentifying one or more accounts (e.g., account 620 of FIG. 6) of users110 of a business entity 160 associated with system 140. In oneembodiment, account information may include financial service accountinformation for a business entity 160 such as a financial institution ora merchant. For example, such account information may includeinformation associated with a checking account, a savings account, acredit account, a debit account, a brokerage account, and any other typeof account provided by business entity 160. In other embodiments,account data 144B may include information identifying investmentportfolios held by one or more customers of business entity 160 (e.g.,positions in one or more securities held by the customers of thefinancial institution).

In some aspects, account data 144B may also include account parameterinformation associated with the one or more accounts of user 110. Forexample, account parameter information consistent with the disclosedembodiments may include, but is not limited to, an account balance, anaccount limit, account identification information (e.g., account number,expiration date information, and/or card security code data), and otherparameters associated with an account held by user 110.

In other instances, the account parameter information may reflect acurrent usage and/or a remaining available usage of the one or moreaccounts. For example, user 110 may hold a debit card issued by thefinancial institution, which may provide a predetermined number of“free” transactions involving the debit card at participating ATMs(e.g., a predetermined number of withdrawal transactions withoutaccruing fees). In certain aspects, the account parameter informationmay identify a number of transactions involving the debit card at theparticipating ATMs, a number of remaining free transactions, and anyadditional or alternate parameters describe user 110's current orremaining available usage.

Further, in additional embodiments, user 110 may participate in loyaltyand/or rewards programs (e.g., referred to collectively as “loyaltyprograms”) provided by the financial institution, and additionally oralternatively, by one or more physical or electronic retailersassociated with business entity 160. In some aspects, account data 144Bmay include information identifying the one or more loyalty programs inwhich the user participates and account information associated with theone or more loyalty programs (e.g., account numbers, account holders,addresses, etc.). Account data 144B may also include informationidentifying one or more parameters of the loyalty programs. Loyaltyprogram account parameters consistent with the disclosed embodimentsinclude, but are not limited to, a current balance of points associatedwith the loyalty programs (e.g., “loyalty points”), a number of loyaltypoints required to achieve one or more rewards or dividends, informationidentifying an impact of specific purchases on user 110's accruedloyalty points (e.g., a loyalty program may accrue double points basedon purchases of specific good and/or specific retailers), and numbers ofloyalty points remaining before user 110 achieves one or more rewards.In certain aspects, the loyalty program information and/or loyaltyprogram parameter information may enable system 140 and/or client device104 to determine an impact of a potential purchase on user 110's loyaltypoints and determine whether the potential purpose would enable user 110to achieve a reward.

In other aspects, account data 144B may include account informationassociated with other types of accounts, such as student meal plans,gift cards, store credit, wireless communications plans, or any otherkind of account capable of maintaining a balance associated with system140. For example, account data 144B may include information associatedwith a meal plan on system 140 for a student at a university (e.g.,business entity 160). In another example, account data 144B may includeinformation associated with a gift card for customer 110 on a merchant's(e.g., business entity 160) system 140. Further, in some instances,account data 144B may include information associated with a wirelessplan (e.g., cellular telephone and data) provided by a wireless carrier(e.g., business entity 160).

In some aspects, the account information may reflect one or more accountparameters associated with current or remaining usage of the account fora service. For example, account parameters consistent with the disclosedembodiments may identify transportation credits used to gain access topublic transportation (e.g., bus, train, etc.), a number of mealsremaining on the student's meal plan, a number of cellular minutes, textmessages, and/or data remaining on user 110's wireless plan, etc.

Transaction data 144C may include information reflecting one or moretransactions involving one or more accounts associated with businessentity 160 and/or system 140. For example, transaction data 144C mayrelate to one or more purchase transactions involving an accountassociated with a user (e.g., user 110) and provided by business entity160. Transaction data 144C may also include information relating toactivities associated with one or more accounts provided by businessentity 160 and processed by system 140. For example, transaction data144C may include data reflecting past bill payments that occurelectronically through online bill payment processes provided by system140. The data may include information such as payment amount, payee,date(s) of payments, descriptions of the type of payment and/or payee,etc. Transaction data 144C may also include information related to priortransactions, historical transactions, or scheduled transactionsassociated with one or more accounts provided by business entity 160.

In other aspects, transaction data 144C may include informationidentifying one or more potential transactions involving one or moreaccounts of business entity 160 associated with system 140. In oneembodiment, potential transactions may include, but are not limited to,potential purchase transactions (e.g., purchases of goods and/orservices from electronic or physical retailers), potential financialservice transactions (e.g., fund transfers), potential bill paymenttransactions (e.g., electronic bill payment transactions), potentialfinancial instrument or security transactions (e.g., purchases ofsecurities), potential deposits or withdrawals of funds, or potentialapplications for credit from the financial institution or other entity.In certain aspects, system 140 may receive from client device 104information reflecting a potential purchase transaction involving one ormore accounts associated with one or more users (e.g., user 110). System140 may store the potential purchase transaction information astransaction data 144C for respective users. In other aspects, system 140may execute software processes that track the potential purchasetransactions for respective account(s), determine and maintain a runningtotal of purchase price(s) associated with goods/services associatedwith the potential purchase transactions on an account basis, a userbasis (e.g., multiple accounts held by a user), or other dataconfigurations.

Client device 104 may include one or more client devices. In certainembodiments, client device 104 may be associated with one or more users110. In one example, user 110 may use client device 104 to perform oneor more processes consistent with the disclosed embodiments. Clientdevice 104 may include, but is not limited to, a personal computer, alaptop computer, a tablet computer, a notebook computer, a hand-heldcomputer, a personal digital assistant, a portable navigation device, amobile device (e.g., mobile phone), a wearable device (e.g., a smartwatch, a wearable activity monitor, wearable smart jewelry, and glassesand other optical devices that include optical head-mounted displays(OHMDs), an embedded device (e.g., in communication with a smart textileor electronic fabric), a set top box, an optical disk player (e.g., aDVD player), a digital video recorder (DVR), and any other computingdevice. In other instances, client device 104 may include opticaldevices capable of providing a “heads-up” display to user 110 (e.g.,vehicle-based heads-up displays), and other optical devices capable ofpresenting an augmented reality (AR) view that “pop-ups” within a fieldof view of user 110. In additional instances, the heads-up displayand/or the AR view provided by the optical devices may modify an objectvisible within user 110's environment (e.g., an “in-view” object withinuser 110's field-of-view, and additionally or alternatively, within animage or video presented user 110 by the optical devices) to indicate astatus of an account of user 110 by, for example, generating andpresenting information that “overlays” a portion of the in-view object(e.g., overlaying interface element over a top portion of the in-viewobject, surrounding the in-view object, and/or within the in-viewobject). In certain aspects, client device 104 may blendcomputer-generated graphics with user 110's real-world or virtualenvironments to visually indicate a status of one or more of user 110'saccounts. Client device 104 may be implemented with one or moreprocessors or computer-based systems, such as for example, computersystem 200 of FIG. 2.

Communications network 120 may include one or more communicationnetworks or medium of digital data communication. Examples ofcommunication network 120 include a local area network (“LAN”), awireless LAN, a RF network, a Near Field Communication (NFC) network,(e.g., a “WiFi” network), a wireless Metropolitan Area Network (MAN)connecting multiple wireless LANs, NFC communication link(s), and a widearea network (“WAN”), e.g., the Internet. Consistent with embodiments ofthe present disclosure, communications network 120 may include theInternet and any publicly accessible network or networks interconnectedvia one or more communication protocols, including, but not limited to,hypertext transfer protocol (HTTP) and transmission controlprotocol/internet protocol (TCP/IP). Communications protocols consistentwith the disclosed embodiments also include protocols facilitating datatransfer using radio frequency identification (RFID) communicationsand/or NFC. Moreover, communications network 120 may also include one ormore mobile device networks, such as a GSM network or a PCS network,allowing client device 104 to send and receive data via applicablecommunications protocols, including those described herein.

Although FIG. 1 illustrates computing environment 100 with one clientdevice 104, the disclosed embodiments may include a plurality of clientdevices 104. Similarly, while FIG. 1 depicts computing environment 100with a single system 140 and user 110, persons of ordinary skill in theart will appreciate environment 100 may include any number of systems140 and users 110, which may be associated with one or more clientdevices 104. In one embodiment, a single business entity 160 may employseveral systems 140 that may communicate with each other (e.g., over aLAN, WAN, or other communications network 120). System(s) 140 may alsobe configured to communicate with one or more other systems, which mayor may not be associated with other business entities.

Further, in some aspects, client device 104 may be configured toestablish peer-to-peer communications sessions with other client devicesdisposed within computing environment 100 (e.g., “connected devices”)using one or more of the communications protocols outlined above. Forexample, client device 104 and the connected devices may be uniquelyidentifiable and addressable within communications network 120, and maybe capable of transmitting and/or receiving data across the establishedcommunications sessions. Further, in some aspects, client device 104 maybe configured to establish the communications sessions with one or moreof the connected devices, and to exchange data with the connecteddevices autonomously and without input or intervention from a user ofclient device 104 (e.g., user 110). For instance, the disclosedembodiments may enable client device 104 to receive data from system140, to identify a connected device capable of receiving transmitteddata from client device 104, and further, to autonomously transmit thereceived data (e.g., to “push” the received data) to the identifiedconnected device without input from user 110. By way of example,connected devices consistent with the disclosed embodiments may include,but are not limited to mobile communications devices (e.g., mobiletelephones, smart phones, tablet computers, etc.) and other devicescapable of communicating with client device 104 (e.g., internet-readytelevisions, internet-ready appliances and lighting fixtures, computingdevices disposed within motor vehicles, etc.).

FIG. 2 illustrates an exemplary computer system 200 with whichembodiments consistent with the present disclosure may be implemented.In certain embodiments, computer system 200 may reflect computer systemsassociated with server 142 or client device 104. In certain embodiments,computer system 200 may include one or more processors 202. Processor202 may be connected to a communication infrastructure 206, such as abus or communications network, e.g., a communications network 120depicted in FIG. 1.

Computer system 200 may also include a main memory 208, for example,random access memory (RAM), and may include a secondary memory 210.Memory 208 may represent a tangible and non-transitory computer-readablemedium having stored therein computer programs, sets of instructions,code, or data to be executed by processor 202. Secondary memory 210 mayinclude, for example, a hard disk drive 212, and/or a removable storagedrive 214, representing a magnetic tape drive, flash memory, an opticaldisk drive, CD/DVD drive, etc. The removable storage drive 214 may readfrom and/or write to a removable storage unit 218 in a well-knownmanner. Removable storage unit 218 may represent a magnetic tape,optical disk, or other storage medium that is read by and written to byremovable storage drive 214. Removable storage unit 218 may represent atangible and non-transitory computer-readable medium having storedtherein computer programs, sets of instructions, code, or data to beexecuted by processor 202.

In alternate embodiments, secondary memory 210 may include other meansfor allowing computer programs or other program instructions to beloaded into computer system 200. Such means may include, for example, aremovable storage unit 222 and an interface 220. An example of suchmeans may include a removable memory chip (e.g., EPROM, RAM, ROM, DRAM,EEPROM, flash memory devices, or other volatile or non-volatile memorydevices) and associated socket, or other removable storage units 222 andinterfaces 220, which allow instructions and data to be transferred fromthe removable storage unit 222 to computer system 200.

Computer system 200 may also include one or more communicationsinterfaces, such as communications interface 224. Communicationsinterface 224 allows software and data to be transferred betweencomputer system 200 and external devices. Examples of communicationsinterface 224 may include a modem, a network interface (e.g., anEthernet card), a communications port, a PCMCIA slot and card, etc.Communications interface 224 may transfer software and data in the formof signals 226, which may be electronic, electromagnetic, optical orother signals capable of being received by communications interface 224.These signals 226 may be provided to communications interface 224 via acommunications path (i.e., channel 228). Channel 228 carries signals 226and may be implemented using wire, cable, fiber optics, RF link, and/orother communications channels. In a disclosed embodiment, signals 226comprise data packets sent to processor 202. Information representingprocessed packets can also be sent in the form of signals 226 fromprocessor 202 through communications path 228.

In certain embodiments in connection with FIG. 2, the terms “storagedevice” and “storage medium” may refer to particular devices including,but not limited to, main memory 208, secondary memory 210, a hard diskinstalled in hard disk drive 212, and removable storage units 218 and222. Further, the term “computer-readable medium” may refer to tangibledevices including, but not limited to, a hard disk installed in harddisk drive 212, any combination of main memory 208 and secondary memory210, and removable storage units 218 and 222, which may respectivelyprovide computer programs and/or sets of instructions to processor 202of computer system 200. Such computer programs and sets of instructionscan be stored within one or more computer-readable media. Additionallyor alternatively, computer programs and one or more sets of instructionsmay also be received via communications interface 224 and stored on theone or more computer-readable media.

Such computer programs and instructions, when executed by processor 202,enable processor 202 to perform one or more processes consistent withthe disclosed embodiments. Examples of program instructions include, forexample, machine code, such as code produced by a compiler, and filescontaining a high-level code that can be executed by processor 202 usingan interpreter.

Furthermore, the computer-implemented methods of the disclosedembodiments may be performed via one or more processors of a single ormultiple computer systems, such as processor 202 of system 200.

In certain aspects, the disclosed embodiments include systems andmethods for providing account status notifications. In one embodiment,account status notifications may be provided in the form of accountstatus indicators. In one aspect, system 140 may perform processes thatgenerate and provide account status indicators to client device 104 forpresentation. In another aspect, system 140 may generate account statusnotification information that is provided to client device 140 forgenerating and presenting account status indicators. Client device 104may be configured to execute software instructions that performoperations, such as generating account status indicators based onaccount status notification information or account information receivedfrom system 140. An account status indicator may be associated with oneor more accounts, and an account may be associated with one or moreaccount status indicators. The one or more accounts may be associatedwith a single user 110. Alternatively, the one or more accounts may beassociated with one or more users 110. In one embodiment, an accountstatus indicator may represent information associated with one or moreaccounts provided by system 140 and/or business entity 160 andassociated with one or more users (e.g., user 110).

In certain embodiments, an account status indicator may reflect thestatus of one or more account parameters of one or more accounts, suchas an account balance, account usage, credit balance, one or morethresholds associated with such parameters, etc. In certain aspects, anaccount status indicator may be a visual indicator, an audio indicator,and/or a tactile indicator (e.g., a vibrate feature). For example, anaccount status indicator may include a graphical representation thatvisually reflects the status of one or more parameters of one or moreaccounts. Examples of graphical account status indicators may includeicons that are displayed on an interface of a display device, such as adisplay of a mobile device (e.g., client device 104). The icon may takethe shape of an image corresponding to business entity 160 (e.g.,corporate logo, or other representation). A graphical account statusindicator may also include a status bar, dashboard type graphicalimages, glyphs, personal photos, and any other type of graphicalrepresentation that may be displayed on an interface. The graphicalrepresentations may be color coded, such that, for example, the accountstatus indicator dynamically changes based on the status of one or moreaccount parameters associated with one or more accounts. An audioaccount status indicator may include a sound or sequence of sounds,music, etc. that may be presented through a speaker of client device104, for example. In one aspect, an audio account status indicator maydynamically change (e.g., change sound(s), music, etc.) based on thestatus of one or more account parameters associated with one or moreaccounts. The above examples are not limiting to the type,configuration, format, and representations of account status indicatorsconsistent with the disclosed embodiments.

In certain aspects, system 140 may be configured to generate anindicator and send the indicator to client device 104. The generatedindicator may represent information associated with one or moretransaction accounts including past, present, predicted, predefined, orpotential effective balances for the one or more transaction accounts.The generated indicator may also incorporate potential transactionsaffecting the one or more transaction accounts associated with user 110.The indicator may take the form of pictorial, audible, or tactileresponses consistent with disclosed embodiments.

In one aspect, the disclosed embodiments may allow one or more accountstatus indicators to be presented in a non-obtrusive manner. Forexample, the disclosed embodiments may allow one or more account statusindicators to be presented without a user request for the status of oneor more parameters of one or more accounts. For instance, client device104 may be configured to automatically present an account statusindicator reflecting the status of an account parameter for an accountassociated with user 110, such as updating the color, format,configuration, size, etc. of a graphical representation on an interfacedisplayed on a display device of client device 104. Further, aspects ofthe disclosed embodiments may allow characteristic(s) of an accountstatus indicator to reflect one or more account parameters in relationto one or more thresholds. As an example, a graphical account statusindicator may change color or size, etc. when an account balance fallsbelow, is equal to, or exceeds a determined balance threshold amount ora balance threshold range(s) (e.g., green, yellow, red).

The disclosed embodiments may also facilitate a presentation of accountstatus indicators based on geographic position information associatedwith user 110 and/or client device 104. For example, client device 104may be configured to present one or more of the account statusindicators when system 140, and additionally or alternatively, clientdevice 104, determines that a current geographic position of user 110falls within a predefined geographic region or is disposed proximate toa predefined geographic location (e.g., a point-of-interest, a retailer,a bus stop or train station, etc.). In further aspects, system 140 (andadditionally or alternatively, client device 104) may be configured toselect an account status indicator for presentation based on arelationship between the account status indicator and a currentgeographic position of user 110. For example, system 140 and/or clientdevice 104 may select, for presentation to user 110, an account statusindicator associated a merchant's loyalty program when user 110 isdisposed proximate to a physical location of the merchant. Other aspectsof account status indicators are described herein and the above examplesare not limiting to the disclosed embodiments.

FIG. 3A shows a flowchart of an exemplary account status notificationconfiguration process 300A consistent with disclosed embodiments. In oneembodiment, process 300A may be performed by system 140. System 140 maybe configured to generate and provide access to a configuration processthat allows a user (e.g., user 110) to configure and control how accountstatus notifications are provided for one or more accounts. In oneaspect, system 140 may generate one or more interfaces that enable user110 to select and/or provide controls defining the type of accountstatus indicator(s) that may be presented via client device 104 (e.g.,select graphical indicators and/or audio indicators, etc.) System 140may provide options in the form of menus, hyperlink selections,user-provided representations, etc. Further, system 140 may allow user110 to define one or more threshold values that determine when and howone or more account status indicators will be presented.

Referring to FIG. 3A, in one embodiment system 140 may generate andprovide account status notification configuration option(s) (step 310A).Account status notification configuration option(s) may includeselections of account status indicator types and selections of accountstatus notification parameter(s). For instance, user 110 may select, viathe option(s), one or more account status indicators. System 140 mayalso allow user 110 to select one or more accounts to be associated withthe selected one or more account status indicators. The selected one ormore accounts may be account(s) associated with user 110 or may be oneor more accounts associated with a different user (e.g., a familymember, employee, etc.)

In response to the configuration option(s), user 110 may select and/ordefine one or more account status configuration option(s). System 140may obtain the selected one or more account status configurationoption(s) from client device 140 or other system associated with user110 (step 320A). System 140 may associate the selected notificationconfiguration option(s) with the user 110's selected one or moreaccounts (step 330A). Based on the determined account statusindicator(s) and configuration option(s), system 140 may configure oneor more notification rule(s) to apply to the one or more accounts andassociated account status indicators identified by user 110 during theconfiguration process 300A (step 340A).

As explained, the disclosed embodiments may allow a user to configurethe manner and way account status notifications may be determined,provided, and presented. For example, the disclosed embodiments mayallow a user to customize the format and way an account status indicatorchanges when an update to the indicator is to occur. For instance, auser may select colors of graphical indicators for different statuslevels (e.g., green for above a threshold, red for below, etc.). Incertain aspects, the disclosed embodiments may allow a user to chooseone or more colors for the graphical indicators. As another example, thedisclosed embodiments may allow a user to configure the notificationssuch that a graphical indicator, such as an icon, can change format ortype. For instance, a user may, through the configuration process 300A,configure the notification for an account to allow an icon background tochange to a selected picture from the user's photo album stored onclient device 104 when the account status indicator is to be updated. Incertain aspects, using symbols, glyphs, pictures, or other types ofimages to reflect certain status levels for one or more parameters of anaccount may provide increased security of the information should theaccount status indicator be viewed by another person viewing the displayof client device 104 when the account status indicator is displayed. Forinstance, user 110 may configure a status notification for a firstaccount such that a default icon image changes to a first image (e.g.,picture of a family member) when a first account parameter is above adetermined threshold (e.g., account balance is above or equal to $200).The default icon may also be configured to change to a second image whenthe first account parameter is below the determined threshold (e.g.,account balance is below $200).

FIG. 3B shows a flowchart of an exemplary account status notificationprocess 300B consistent with disclosed embodiments. In one example,system 140 may obtain transaction data associated with one or moretransactions involving one or more of the selected one or more accountsidentified in the configuration process 300A (step 310B). For example,user 110 may use a first account to purchase goods from one or moremerchants. System 140 may receive transaction data associated with thepurchase(s) from, for example, merchant systems associated with themerchant(s) involved in the transaction. The disclosed embodiments mayalso obtain transaction data in other ways. System 140 may perform anaccount status notification process based on the obtained transactiondata (step 320B). In one embodiment, system 140 may determine changes toone or more parameters of the user's selected one or more account(s)based on the transaction data (e.g., determine updated balance(s),updated credit limit(s), etc.). Based on the results from that analysis,system 140 may execute software instructions that perform processes thatapply the one or more notification rule(s) determined in process 300A.For example, depending on the type of notification that user 110 mayhave configured, system 140 may determine a current balance of a firstaccount (e.g., a checking account held by user 110 or an accountassociated with a loyalty program in which user 110 participates) afterone or more purchase transactions reflected in the obtained transactiondata. System 140 may apply the rule(s) to compare determined current oneor more account parameter(s) (e.g., balance, remaining usage, loyaltyprogram points, etc.) against one or more threshold values or ranges todetermine whether an account status indicator is to be generated orupdated. Based on that analysis, system 140 may generate or update oneor more account status indicator(s) associated with the account(s) underanalysis (step 330B). System 140 may provide the generated or updatedaccount status indicator(s) for presentation (step 340B). For example,system 140 may provide an updated account status indicator to clientdevice 104 that is displayed on an interface of client device 104without a user request for an account status.

In certain embodiments, system 140 may be configured to generate accountstatus notification information that is used to generate account statusindicator(s) at the client device 104. In another aspect, client device104 may be configured to execute software processes that perform processsteps 320B-340B based on account information provided by system 140. Forexample, in one embodiment, system 140 may perform account statusnotification process (step 320B) and provide notification information toclient 104. Client device 104 may generate or update one or more accountstatus indicator(s) based on the notification information and one ormore configuration rule(s) defined during configuration process 300A. Inanother embodiment, client device 104 may obtain account informationfrom system 140 (e.g., account balance information, usage data, etc.).Based on the account information, client 104 may perform an accountstatus notification process (e.g., step 320B) and generate or updateaccount status indicator(s) (e.g., step 330B) for presentation by clientdevice 104 (e.g., step 340B).

FIG. 3C shows a flowchart of an exemplary process flow consistent withdisclosed embodiments. The process flow of FIG. 3C shows exemplaryoperations and exemplary relationships between operations that may beperformed by system 140 and a client device (e.g., client device 104).The disclosed embodiments are not limited to the exemplary operationsand the relationships shown in FIG. 3C. Further, one or more of theoperations and/or one or more relationships between the operations shownin FIG. 3C may be optional, not implemented, or performed in a differentprocess relationship than that illustrated in FIG. 30. For example,where client device 104 may be configured to generate or update accountstatus indicators, or determine the status of one or more accountparameters, system 140 may not be required to perform those operationsfor selected accounts. Further, in configurations where system 140generates and provides account status indicator(s) to client device 104,the same operations may not be performed by client device 104.

FIG. 3D illustrates a flowchart of another exemplary process 300D forproviding one or more generated or updated (from a previously generated)account status indicators for presentation by client device 104consistent with disclosed embodiments. Exemplary method 300D may providethe functionality enabling client device 104 or server 142 of system 140to generate or update an account status indicator for presentation byuser device 104. In some aspects, system 140 may be configured toexecute software instructions to obtain balance data associated with oneor more accounts associated with user 110 (step 310D). System 140 mayobtain the balance data from server 142, data repository 144, clientdevice 104, or another system. As previously discussed, balance data mayinclude customer data 144A, account data 144B, transaction data 144C, orany combination thereof. In another embodiment, client device 104 may beconfigured to obtain the balance data associated with one or moreaccounts associated with user 110.

System 140 may also be configured to calculate an account balance forone or more accounts associated with user 110 (step 320D). For example,system 140 may determine the account balances for a set of accounts thathave been selected by user 110 during a configuration process (e.g.,process 300A). System 140 may be configured to execute softwareinstructions for calculating the account balance for certain accountsusing the obtained balance data. In one embodiment, system 140 mayselect one or more portions of the balance data to compute an accountbalance for the associated one or more accounts. The disclosedembodiments are not limited to the portions of balance data used tocalculate the account balance, nor are they limited in kind or number tothe accounts that system 140 may process to determine accountbalance(s).

In certain embodiments, system 140 or client device 104 may calculateaccount balances for associated accounts using one or more factors. Forexemplary purposes only, the present disclosure may refer to these typesof account balances as effective account balances. Examples of effectiveaccount balances include account balances that may be calculated basedon one or more past, present, predicted, predefined, or potentialconditions. For example, in some embodiments, an effective accountbalance may consist of the actual balance of an account. In otherembodiments, the effective account balance may use the actual accountbalance in conjunction with estimated expenses, payments, or potentialpurchases. In other aspects, the effective account balance may not usethe actual account balance at all, and may instead use some combinationof the above conditions consistent with the disclosed embodiments.

System 140 may be configured to determine whether to send an accountstatus indicator to client device 104. As previously discussed, incertain embodiments, the account status indicator may reflect a statusof one or more accounts associated with one or more users (e.g., user110). In some embodiments, system 140 may determine whether to send theindicator to client device 104 based on whether a status of one or moreaccount parameters of one or more accounts associated with one or moreaccount status indicators has changed (step 330D). In some aspects, anexisting account status indicator may change based on received thereceived balance data from step 310, one or more effective accountbalance(s) that may be calculated in step 320, or both. By way ofexample, system 140 may determine the account status indicator for aparticular account has changed when the funds (or other type of accountelement) available in an account fall below, exceeds, and/or equal tobelow one or more threshold values (e.g., $200) or is within a range ofthreshold value(s) (e.g., $200 to $400).

If system 140 determines that the status for the account statusindicator status has changed for one or more indicators, system 140 maybe configured to send an updated indicator to client device 104 (step340D). System 140 may be configured to execute software instructions forsending the updated account status indicator to device 104 based onwhether the indicator status of one of the indicators has changed (e.g.,step 330D). In other embodiments, as discussed above, system 140 maygenerate and provide account status notification information (e.g.,account balance information, etc.) that client device 104 may use togenerate or update the account status indicator for the associatedaccount(s).

In other embodiments, system 140 may be configured to receive balancedata (step 310D), compute one or more effective account balances (step320D), determine whether the generate an updated account statusindicator based on the effective account balance(s) (step 330D) and sendthe updated account status indicator to client device 104 (step 350D).In certain aspects, the disclosed embodiments allow client device 104(or other system or device that receives the account status indicator)to automatically present the generated or updated account statusindicator without any input from user 110, such as, for example, logginginto an account and checking an account balance or other accountparameter for the associated account.

In certain aspects, client device 104 may be configured to obtain theupdated indicator from system 140 without any input from a user. Forexample, system 140 may push the account status indicator to clientdevice 104 without a user request to obtain account information, statusinformation, etc. Further, as mentioned, client device 104 may beconfigured to generate and/or update account status indicator(s) for oneor more accounts associated with user 110. In one aspect, based on theupdated account status indicator obtained from system 140, client device104 may present the updated account status indicator (step 350D). Clientdevice 104 may present the account status indicator visually or audiblydepending on the configuration of the account status indicator definedduring the configuration process 300A. Alternatively, system 140 mayconfigure account status indicators using default indicators (graphicalor audio).

FIG. 4 depicts an exemplary client device 104 consistent with certaindisclosed embodiments. In one embodiment, client device 104 may be asmartphone with a display device having touchscreen capabilities viaviewing pane 406. Client device 104 may be any type of computing device,however, and the representation of FIG. 4 is for exemplary purposesonly. In the exemplary FIG. 4, client device 104 may include one or moreviewing panes 406 that display on an interface one or more graphicalrepresentations, such as icon 402. In some aspects, icon 402 maycomprise only a portion of the viewing pane 406 of client device 104(e.g., as depicted in FIG. 4). In other embodiments, icon 402 maycomprise the entire viewing pane 406 of client device 104. In yet otherembodiments, icon 402 may comprise no portion of the viewing pane 406.Similarly, viewing panes 406 may constitute none, some, or all of one ormore surfaces of client device 104.

In some embodiments, icon 402 may include one or more account statusindicators 404 associated with one or more accounts. In otherembodiments, icon 402 may represent an account status indicator. Thenumber and type of indicators displayed within icon 402 may vary basedon the configuration of the status notification aspects for one or moreassociated accounts, and/or based on the status of one or more accountparameters that are monitored for status notifications. As described inexemplary embodiments below, for example, a user may configure thestatus notification for one or more accounts such that an account statusindicator(s) is presented that alerts a change in one or more accountparameters associated with the one or more accounts. As explained, thealert provided by the account status indicator may take the form of atactile mechanism (e.g., a vibrate feature) or audio mechanism (e.g.,music or sounds), in which case a pictorial representation of theindicator may be unnecessary. In other embodiments, icon 402 maygraphically depict one or more account status indicators 404 dependingon the status of the one or more account parameters for the one or moreassociated accounts. For instance, account status indicator 404 maychange based on balance data or effective account balances of one ormore associated accounts.

FIGS. 5A-5F illustrate exemplary graphical indicators and/or accountstatus indicators. In accordance with certain embodiments, the manner,timing, and appearance of an account status indicator may depend in parton, for instance, the status of one or more account parametersassociated with one or more associated accounts, indicator type,notification rule(s), etc. For example, FIG. 5A shows an exemplary iconincluding multiple account status indicators 502, 504 taking the form ofcolored status bars (e.g., status bar indicators). In certain aspects,account status indicators 502, 504 may be associated with the status ofa respective account parameter of a single account. For instance,indicator 502 may reflect the status of an account balance and indicator504 may reflect the status of a credit limit of the account. In otherinstances, indicator 502 may reflect a status of a balance of pointsavailable to user 110 through a corresponding loyalty program, andindicator 504 may reflect a number of points required for user 110 toobtain a reward associated with the corresponding loyalty program.

In other aspects, account status indicator 502 may reflect an accountparameter of a first account and account status indicator 504 mayreflect an account parameter of a second account. The first and secondaccounts may be associated with a single user (e.g., user 110), or thefirst account may be associated with a first user and the second accountmay be associated with different users. Further, the account parameterthat is associated with the status reflected in the first and secondaccount indicators may be the same account parameter (e.g., accountbalance or points balance), of the account parameter associated withstatus indicator 502 may be a different account parameter than theaccount parameter associated with status indicator 504. The disclosedembodiments may include more than two account status indicators eachrelating to account parameter(s) of a single or separate accounts. Thedisclosed embodiments may allow a user to configure the number, format,and associations of account status indicators in the configurationprocess 300A.

In certain embodiments, the properties of each account status indicator502, 504 may change according to the status of the one or more accountparameters associated with the indicators. In other aspects, theproperties of each account status indicator 502, 504 may changeaccording to the status of an effective account balance associated withthe one or more accounts relating to the indicators. In one embodiment,the properties of a bar indicator may vary with respect to its indicatorstatus derived from an indicator rubric incorporating one or moreeffective account balances. System 140 or client device 104 may beconfigured to execute software instructions that perform processes thatenable user 110 to establish one or more rules comprising the indicatorrubric governing the indicator status, such as during configurationprocess 300A. In some embodiments, the exemplary status bar indicators502, 504 may change size (e.g., width, length, height, etc.), color(e.g., green, red, etc.), fill effects (e.g., solid, striped, dotted),and/or transparency (e.g., alpha) based on an indicator status derivedfrom an underlying indictor rubric. For example, user 110 may wish toset up a bar indicator associated with a single account such that thebar appears red when the effective account balance of the account fallsbelow a defined threshold. In this example, the user may further definethe indicator rubric to color the bar indicator green when the effectiveaccount balance exceeds the threshold, turn yellow when the balance iswithin a certain range of the threshold, incorporate both effects, andthe like.

The disclosed embodiments allow for different account status indicatorformats, types, size, and color schemes that will be readily apparent tothose skilled in the art. For instance, the disclosed embodiments mayconfigure an account status bar indicator such that a color gradient iscontinuous instead of discrete (e.g., the entire visual spectrum betweentwo defined points). Additionally or alternatively, the exemplary barindicators 502, 504 may elongate or contract (e.g., a small or “empty”bar for low effective account balances and a long or “full” bar for highbalances) depending on the underlying rubric (e.g., bar 502). Theexemplary bar indicators 502, 504 may also be configured to spanhorizontally or vertically. Moreover, system 140 may provide processesthat enable user 110 to configure the status notification such thatmultiple bar indicators appear in parallel or in series, such that, forinstance, a single bar includes two bar indicators, each associated withtheir own accounts.

FIG. 5B illustrates another exemplary account status indicatorconsistent with disclosed embodiments. In FIG. 5B, the exemplary accountstatus indicator may be in the form of a pie chart (“pie indicator”)whose properties may vary according to one or more associatednotification rules, indicator rubrics, and/or statuses of one or moreaccount parameters of one or more associated accounts. As discussed inreference to FIG. 5A, user 110 may establish one or more notificationrules comprising the indicator rubrics governing the presentment of theexemplary account status indicator. In some embodiments, a pieindicator, or a portion of the pie indicator, may change color (e.g.,green, red), fill effects (e.g., solid, striped, dotted), relative size,and/or transparency (e.g., alpha) based on the status of one or moreaccount parameters, such as, for example, an account balance, a balanceof points available through a loyalty program, an effective balance ofthe accounts, an effective balance of a loyalty program account (e.g.,an effect of a potential purchase of a product on the loyalty programaccount), relative size of the included indicators. The indicator may becolored, filled, sized, and shaded in any of the manners previouslydescribed.

Taking FIG. 5B as an example, during the configuration process 300A, asystem 140 may perform processes that enable user 110 to define threeaccount status indicators in a pie indicator arrangement, where eachportion of the pie indicator arrangement is associated with a singleaccount, or each portion may be associated with a separate account, ortwo portions may be associated with a single account and the thirdassociated with a different account. In the example shown in FIG. 5B,the user may have defined each status indicator to comprise equal areasof the pie indicator, although the user need not define the pieindicator in this way. In this example, the user may elect to color orshade each of the account status indicators included in the pie statusindicator based on preferences, notification rules, rubrics, etc. thattake into account one or more account parameters (e.g., effectiveaccount balances). As shown in FIG. 5B, for example, each account statusindicator 506, 507, 508 in the pie indicator may have its own coloringand/or shading scheme that may change based on a status of one or moreaccounts associated with a respective account status indicator. Inaddition, in one aspect, the pie indicator may be included in an icon.

FIG. 5C illustrates another exemplary account status indicator iconconsistent with certain embodiments. In this embodiment, the accountstatus indicator may be included in an icon such that it encompasses theentire or a portion of the background of the icon (e.g., backgroundindicator). In some embodiments, the color, fill effects, and/ortransparency of the background indicator may vary according to thestatus of one or more parameters associated with an account relating tothe indicator. In certain aspects, system 140 may be configured to allowuser 112 to select the color of the background indicator (e.g., red,green, etc.) to be used when a notification status is to be providedbased on a status of one or more parameters of the associatedaccount(s), such as an effective balance, balance data, loyalty programdata, current or remaining usage data, etc.

FIG. 5D illustrates another exemplary embodiment of an account statusindicator consistent with certain embodiments. The disclosed embodimentsmay provide an account status indicator in the form of a picture(picture indicator), symbol (symbol indicator), or glyph (glyphindicator). FIG. 5D shows an example of a glyph indicator. In certainaspects, properties of the glyph indicator (e.g., colors, animation,size, shape, type, etc.) may change according to one or more accountparameters of one or more associated accounts, such as effective accountbalances. In some embodiments, the glyph indicator may change betweenindicator types. This feature is not unique to glyph indicators as thedisclosed embodiments may allow any type of account status indicator tobe replaced with a second type of account status indicator as a way ofreflecting a status of one or more account parameters of one or moreaccounts (e.g., switch from status bar indicator to background indicatorwhen the status of an account parameter triggers a notification). Forexample, a glyph indicator image (e.g., check mark, large “X,” happyface, cloud, thunderbolt, thumbs up, fuel gauge ticker, stop sign, etc.)or its properties (e.g., size, shape, color, transparency, orientation,position, animation, etc.) may change based on, for example, one or morenotification rules and/or account status notification information. Forexample, user 110 may define a glyph indicator in such a way as todisplay a green check mark when an associated effective account balanceof a monitored account exceeds or equals a threshold value (e.g., athreshold balance of a checking or savings account, or a thresholdbalance of points associated with a loyalty program) and display a red“X” when the effective account balance fall below the threshold value.

FIG. 5E shows an exemplary account status indicator consistent withdisclosed embodiments. The indicator of FIG. 5E may be colored text(e.g., text indicator) that may change based on the status of one ormore parameters associated with one or more accounts. A text indicatorcan include a single line of text that is associated with one account,or a text indicator may include multiple account status indicators inthe form of lines of text that each are associated with one or moredifferent parameters of a single account, or associated with one or moredifferent accounts. For example, in one aspect, each line of text of thetext indicator of FIG. 5E may reflect an account status indicatorassociated with one or more accounts, each with their own accountparameters, such as effective account balances. One or more propertiesof the text may change according to, for example, the effective accountbalances of the associated accounts, which may be defined by one or morenotification rules. In some embodiments, the text may change its font,size, capitalization (e.g., all caps, small caps), style (e.g., bold,underline, italic, etc.), color, transparency, or accompanying glyph asgoverned by the notification rules, which may be configured by a userduring configuration process 300A.

While the foregoing discussion describes account status indicators asvisual indicators, the disclosed embodiments may also implement othertypes of indicators that may consist of nonvisual cues such as musicaltones, songs, vibration, or other non-pictorial elements. The disclosedembodiments may allow client device 104, for example, to present suchindicators based on the same criteria set forth for visual indicators(e.g., notification rules, status of account parameter(s), etc.). Incertain aspects, nonvisual indicators may be presented with visualindicators. For example, FIG. 5F illustrates a visual indicatordisplaying a musical note in an icon. The note may indicate, forinstance, the indicator is set to present certain nonvisual tones ormusic based on statuses of account parameters. When a nonvisualindicator is presented, client device 104 may be configured to present avisual indicator at the same time to provide multiple mechanisms tonotify a user of a change in status of one or more account parametersfor one or more accounts. In some embodiments, client device 104 may notdisplay any indication of a nonvisual indicator at all. For example, anonvisual indicator may alert user 110 of a changed indicator status byplaying a tone, playing a certain song, playing different tones ofdifferent lengths, vibrating in different durations and amplitudes, andthe like.

Moreover, while the foregoing discussion described the various indicatorforms separately, the present disclosure also contemplates combining anynumber of indicator types together (e.g., the glyph and text indicatorsof FIG. 5E). For example, a user could establish a bar indicator, pieindicator, background indicator, glyph indicator, and text indicatorsimultaneously. In such embodiments, one or more of the account statusindicators may correspond to one or more accounts.

Returning to FIG. 4, user 110 may interact with icon 402 in response to,for example, the account status indicator 404. In some embodiments, ifaccount status indicator 404 reflects a particular account status (e.g.,a red bar for a bar indicator), the user may interact with icon 402 toobtain additional information and initiate additional follow-onprocessing. For example, user 110 may notice a bar indicator 404 is red,and such indication may signify that an effective account balance forone or more associated accounts have fallen below a defined threshold asdisclosed herein. In certain embodiments, the user may then interactwith the icon to perform a variety of functions, such as opening a newaccount, extending an account balance, viewing account transactionhistory, or accessing and participating in a configuration process todefine or change properties, rules, and associations of accounts withindicators, etc. (such as the configuration process 300A). It should beappreciated that user 110 may interact with icon 402 for any reason, andneed not be motivated by a particular account status indictor 404.

For example, client device 104 may perform follow-on processes inresponse to the user's selection of the notification icon requestinginput from the user. In some embodiments, these requests may arise viainterface(s) allowing the user to assign an account status indicator toone or more accounts, change an underlying indicator rubric, changerules that affect the balance calculation method for associatedaccounts, and any other such variable change consistent with thedisclosed embodiments. This may allow user 110 to view, inspect, change,or cancel one or more parameters, or value derived from one or moreparameters (e.g., an indicator rubric), in real-time using client device104. For example, a user may physically press icon 402 to viewtransaction history associated with one or more accounts, change anindicator rubric to extend an account balance, change an indicator typeor status, or affect any value derived from one or more accountparameters. In some embodiments, such follow-on processing may beperformed by client device 104, or a server 142 associated with system140, or both.

The disclosed embodiments allow one or more users to be associated withone or more accounts. Further, the disclosed embodiments allow one ormore accounts to be associated with one or more account statusindicators. The one or more account status indicators may correspond toone or more account parameters (e.g., an effective account balance) ofits one or more corresponding accounts. The one or more account statusindicators may also be associated with one or more indicator rubrics,which in one example may define an indicator status based on theeffective account balances of the associated accounts. In certainembodiments, the effective account balances of the associated accountsmay relate to past, present, predicted, predefined, and potentialtransactions.

Furthermore, the disclosed embodiments are not limited to displayableicons (e.g., icon 402 of FIG. 4) that incorporate one or more statusindicators within corresponding icon boundaries (e.g., account statusindicators 502 and 504 of FIG. 5A and/or account status indicators 506,508, and 510 of FIG. 5B). In additional embodiments, client device 104may execute software processes to present, to a user (e.g., throughviewing pane 406 of FIG. 4), an icon surrounded by one or more accountstatus indicators that reflect statuses of account parameters associatedwith one or more accounts. For example, FIG. 5G illustrates an exemplaryaccount status indicator 512 in the form of a “ring” indicator thatsurrounds an outer boundary of an icon 402, and FIG. 5H illustratesexemplary account status indicator 514, 516, and 518 that collectivelyestablish concentric ring indicators surrounding the outer boundary oficon 402. In certain aspects, and as described above in reference toaccount status bar 502 of FIG. 5A, account status indicators 512, 514,516, and/or 518 may reflect the status of an account parameter of asingle account, or may reflect statuses of account parameters ofmultiple accounts (e.g., a total balance, total credit limit, etc., ofmultiple accounts held by user 110).

By way of example, account status indicators 512, 514, 516, and/or 518may reflect the status of an account balance of a checking account heldby user 110, a credit limit of a credit account held by user 110 (e.g.,a Visa™ card issued by a financial institution associated with businessentity 160), a balance of accrued points associated with a loyaltyprogram in which user 110 participates (e.g., a loyalty programsponsored by a merchant), and/or a number of loyalty points remaininguntil user 110 qualifies for a benefit or reward provided by the loyaltyprogram. Further, as described above, client device 104 may beconfigured to modify one or more visual characteristics of accountstatus indicator 512, 514, 516, and 518 to indicate a change in thestatus of the account parameter(s) associated with the indicators (e.g.,an actual or effective balance of a checking, credit, and/or loyaltyprogram account). In some instances, the visual properties of accountstatus indicator 512, 514, 516, and 518 may vary with respect to itsindicator status derived from an indicator rubric incorporating one ormore of the actual or effective account balances (e.g., as establishedby user 110 using the exemplary processes described above). In someembodiments, the exemplary status indicators 512, 514, 516, and/or 518may change size (e.g., width, length, height, etc.), color (e.g., green,red, etc.), fill effects (e.g., solid, striped, dotted), and/ortransparency (e.g., alpha) based on a change in an indicator statusderived from an underlying indictor rubric.

In some aspects, user 110 may, through a graphical user interface (GUI)presented by client device 104, associate account status indicator 514with an effective balance of a checking account, account statusindicator 516 with an effective balance of a credit card account, andfurther, associate account status indicator 518 with an effectivebalance of a loyalty program account. In some instances, user 110 mayestablish threshold balances for each of the checking, credit card, andloyalty programs accounts, and may establish notification rules thatinstruct client device 104 (and/or system 140) to color account statusindicators 514, 516, and/or 518 green when a corresponding one of theeffective account balances exceeds the corresponding threshold balance,and red when the corresponding effective balance falls below thethreshold balance.

Although described in terms of one or three status indicators, thedisclosed embodiments may enable user 110 to establish, through acorresponding GUI, notification rules that configure client device 104to present any additional or alternate number of account statusindicators linked to corresponding account parameters of accounts heldby user 110. In certain aspects, through the GUI, user 110 may add orremove “layers” of concentric account indicators to produce customizednotification rules that enable user 110 to make informed decisionsregarding potential purchases based on impacts of the potential purchaseon various aspects of user 110's current financial situation.

FIG. 6 depicts an exemplary relationship arrangement 600 regarding anexemplary account status indicator implementation, consistent withdisclosed embodiments. In one example, system 140 may be configured toobtain balance data 606 comprising all or a portion of customer data144A, account data 144B, and/or transaction data 144C for one or moreaccounts 620 that may be associated with user 110. Balance data 606 mayinclude information relating to an account batch 610, comprising one ormore user accounts 620 (signified through phantom lines for a secondtransaction account 620 in FIG. 6). The one or more accounts may beassociated with one or more account status indicators 404 that may beconfigured and operate in a manner consistent with the disclosedembodiments. While FIG. 6 depicts at two accounts 620 and indicators404, the disclosed embodiments are not limited to these configurations.Indeed, the disclosed embodiments may be configured to allow user 110 tobe associated with any number of accounts 620 that may relate to otherusers, and those accounts may be associated with any number ofindicators 404.

In the exemplary arrangement 600, account 620 may associate withinformation contained in balance data 606. In some embodiments, account620 may include account balance data 626. Account balance data 626 mayinclude any subset of customer data 144A, account data 144B, andtransaction data 144C (e.g., balance data 606) related to a particularaccount 620. The account balance data 626 may vary according to the typeof associated account. For example, for a particular account 620,account balance data 626 may include information signifying the type ofaccount (e.g., checking, savings, credit card, securities account,college meal plan, store credit, loyalty program, or any such accountpreviously discussed), data associated with the account (e.g., currentbalance, pending transactions, transaction history, other historicaldata, account number, routing number, card number, expiration date,etc.), data associated with the owner or accessor of the account (e.g.,login information, security measures, etc.), and/or transaction datarelated to potential purchases as explained below.

Account 620 may also associate with one or more rules that may relatehow to calculate an effective account balance for the account (e.g.,balance calculation method 624 in FIG. 6). System 140 may performprocess that generate and apply the rules and comprising balancecalculation method 624. In one aspect, system 140 may provide interfacesover network 120 to client device 104 to allow user 110 to define one ormore of these rules. Alternatively, client device 104 may perform suchprocesses.

In some embodiments, balance calculation method 624 may include softwareinstructions that when executed by a processor perform balancecalculation processes consistent with the disclosed embodiments. In oneexample, balance calculation method 624 may comprise a straight balancedetermination. In such embodiments, the effective account balance mayreflect a current available balance for account 620. In otherembodiments, balance calculation method 624 may provide effectivebalances, such as predictive and intelligent balances that aredetermined through predictive and intelligent balance calculationprocesses.

For example, in some embodiments, balance calculation method 624 mayinclude software-based processes that when performed obtains andanalyzes information relating to scheduled future expenses of user 110,(e.g., an upcoming trip, a wedding, a future purchase of a good orservice such as a car, etc.), periodic expenses of user 110 (e.g., amortgage, average weekly grocery bills, average monthly utility costs,annual insurance premiums, rent, etc.), future or periodic wages orother payments relating to user 110 (e.g., a salary, a bonus, averageperiodic pay for hourly workers, annuity payments, etc.), and/orpotential purchases of user 110. This information may be obtaineddirectly from the user 110 via client device 104, through softwareprocesses executed on server 142 associated with system 140, or both. Insome embodiments, for example, a user may input this informationdirectly through processing systems associated with client device 104.Client device 104 or system 140 may then store the user's informationconsistent with the disclosed embodiments. Additionally oralternatively, system 140 may be configured to obtain informationassociated with an account for user 110 without input from the user. Insome aspects, system 140 may be configured to obtain this informationfor an account it itself provides, an account provided by anothersystem, or the like. System 140 may also be configured to sendinstructions to client device 104 designed to query user 110 for suchinformation without prior affirmative input from the user.

In some aspects, for example, user 110 may associate with a checkingaccount associated with system 140 for business entity 160 (e.g., afinancial institution). System 140 of business entity 160 may beconfigured to analyze the purchasing habits of user 110 over a period oftime (e.g., a flat duration, weekly, monthly, user-defined, etc.). Thesystem 140 may analyze a variety of aspects of the user's spendinghabits including the expenditures' source (e.g., by merchant), type(e.g., by product or kind of expense, e.g., groceries, rent, mortgage,etc.), amount, location, or similar characteristic. Based on the resultsof its analysis, system 140 may be further configured to calculate auser's expected expenses resulting from certain sources, certainexpenditure types, certain geographical locations, or all sourcescombined. In this example, for instance, system 140 may calculate auser's monthly expenditures on groceries for which user 110 uses thechecking account associated with financial institution 160. User 110 maythen use the value of these calculated expenses as she defines herbalance calculation method 624. In other embodiments, processes runningon client device 104 may be configured to calculate these expenses.Additionally or alternatively, user 110 may provide the informationdirectly to client device 104 without the need of background processing.

As an illustrative example of some aspects of the disclosed embodiments,user 110 may specify she wishes to calculate an effective accountbalance for account 620 incorporating both her mortgage payment andsalary information in addition to the current account balance. In suchan example, the effective account balance for user 110 may reflect theexisting actual balance of an associated account and a future accountbalance after certain determined periodic (e.g., weekly, monthly,semi-monthly, etc.) expenses and wages. For instance, system 140 mayperform processes that obtain transaction information associated withassociated account(s) for user 110 to determine one or more expensesthat may be configured for automatic payment (e.g., configured bill paymechanisms in online banking portals). As another example, system 140may analyze historical transaction data for the associated account(s) toidentify periodic expenses (e.g., similar payments made to a mortgagelender entity, utility payments, etc.) and determine an average monthlyexpense that applies to an associated account for user 112. Based on thedetermined expenses, system 140 may calculate an effective balance forthe account by subtracting the determined expenses from the actualbalance. The disclosed embodiments may allow the account statusindicator(s) for the account to reflect a status of the calculatedeffective balance, thus providing user 112 with a status of the accountthat takes into consideration known expenses to be withdrawn from theaccount. In one embodiment, a status indicator may simultaneously showthe status of an actual balance and effective balance of an account,through for example, a status bar indicator.

The disclosed embodiments may be configured to enable user 110 or system140 to specify one or more notification rules that may direct thedisclosed processes to determine statuses of one or more accountparameters (e.g., actual and/or effective balances, etc.), not limitedin kind, amount, and/or periodicity. The disclosed embodiments may allowthe configuration of such rules to occur automatically (e.g., as adefault background process performed by system 140 (e.g., duringconfiguration process 300A)), manually (e.g., user 110 inputs theconfiguration input information), or some combination thereof. Thus, asexplained, for example, system 140 may be configured to determine theaverage periodic expenses for user 110 given the user's historicalexpense information (e.g., a mortgage, grocery bills, utility bills,etc.). In one embodiment, system 140 may do so regardless of whetherhistorical expenses are periodic (e.g., a user may not purchasegroceries in a particular week). In one embodiment, user 110 may havecontrol through configuration process 300A what kind of predictivepurchases and payments may be considered for performing a balancecalculation method 626 (e.g., user 110 could override results from abalance calculation process performed by system 140).

In certain embodiments, the status notification aspects of the disclosedembodiments may provide account status notifications based on potentialtransactions (e.g., potential purchase transactions by user 110 that mayaffect an account balance). In one embodiment, for example, balancecalculation method 624 may determine an effective balance (e.g., 620)based on information relating to one or more potential transactions. Inone aspect, this information may subsist in some portion of accountbalance data 626 that may be derived from balance data 606, which inturn may be derived from transaction data 1440. In one embodiment,client device 104 may be configured to communicate transaction data 1440to system 140 in contemplation of potential transactions. Suchcommunication may occur over any communications network (e.g.,communications network 120 of FIG. 1). Contemplated potentialtransactions may include any kind of transaction previously discussed inrelation to transaction data 144C including, but not limited to,potential purchases, fund transfers, bill payments, securitytransactions, and so on.

In some embodiments, client device 104 may be configured to receive,track, and transmit transaction data 144C to system 140 via any networkpreviously discussed. In some embodiments, for example, client device104 may be configured to scan a bar code for one or more particulargoods at a physical retailer and relay the relevant information (e.g.,location, cost of the goods, accounts affected, etc.) to system 140. Inthese embodiments, client device 104 may be configured to obtain suchtransaction data using any method known to those skilled in the art(e.g., NFCs, optical scanners, Bluetooth communications, etc.). Inanother embodiment, a user may instead input such information directlyinto client device 104 without the use of a scanner or code reader.

Moreover, client device 104 may be configured to assimilate andaggregate several potential transactions together, even transactionsaffecting different accounts 620. For example, user 110 may aggregatemultiple potential purchase transactions affecting a first account witha funds transfer for a second account to determine the effect, if any,on the effective balances on those accounts as well as their effects onone or more associated account status indicators 404. The disclosedembodiments may be configured to allow user 110 to incorporate anynumber of potential transactions associated with any number of accounts.Such transactions, if any, may adjust the calculated effective accountbalance for one or more accounts 620, which may in turn change theindicator status 644 of associated indicators 620.

FIG. 6 also illustrates how one or more accounts 620 may be associatedwith one or more account status indicators 404 (e.g., a first accountrelates to two different indicators). Similarly, an account statusindicator 404 may associate with one or more accounts 620 (e.g., thesecond indicator relates to two accounts). An account status indicator404 may further associate with one or more properties. In one example,indicator 404 may include an indicator type property 642. Indicator type642 may include information signifying the form of the indicator whenpresented by client device 104, such as a bar indicator, a glyphindicator, or any combination of pictorial and nonvisual indicatortypes, such as those described in relation to FIGS. 5A-5F. Indicatortype 642 may also include properties signifying how client device 104presents the indicator 404 on client device 104 (e.g., the color of abar indicator, the length of a vibration, a kind of music played, thepictures of a glyph indicator, the fill of a pie indicator, or any otherconfiguration that may be assigned consistent with disclosedembodiments).

Indicator 404 may also include indicator status property 644. In oneaspect, indicator status 644 may include information signifying apresent status of an indicator 404. Indicator status information 644 maydepend in part on the indicator type 642, underlying indicator rubric646, effective account balances of related account(s) 624, other balancedata 626, or other account data. For example, given an indicator rubric646 consistent with disclosed embodiments, an indicator status maysignify a bar indicator is colored green, a glyph indicator is a red“X,” or any other such indicator status described in connection withFIGS. 5A-5F.

An account status indicator 404 may include an indicator rubric property646. In one embodiment, an indicator rubric 646 may include informationthat defines a set of logical rules promulgating how to generate anindicator status 646 for a particular indicator type 642 given one ormore account parameters, such as the effective account balance and/orbalance data for account(s) 620 associated with indicator 404. Thelogical rules associated with indicator rubric 646 may be configured andapplied automatically by system 140 when performing status notificationprocesses consistent with the disclosed embodiments. The logical rulesmay be configured manually from user 110 during a configuration process(e.g., configuration process 300A). By way of example, one exemplaryindicator rubric may, when processed by system 140 and/or client device104, determine to set the color of a bar indicator to “green” when aneffective account balance of an associated account exceeds or is equalto a threshold value. In another example, an indicator rubric may, whenprocesses by system 140 and/or client device 104, change a glyphassociated with a glyph indicator to a another format (e.g., a stormcloud image) if the sum of the effective account balances for allassociated accounts drops below a threshold value, which may result fromconsiderations of monthly expenses, income, and/or potential purchasesassociated with the account.

Consistent with the disclosed embodiments, rubric indicator 646 mayprovide a hierarchy of rules providing for multiple possible outcomes(e.g., multiple coloring schemes, several pictures, etc.). Furthermore,while embodiments of indicator rubric 646 may employ some aspect of theeffective account balance for associated accounts, certain embodimentsof the present disclosure may eschew the effective account balanceentirely, generating an account status indicator from balance data(e.g., potential transactions, monthly expenses in relation to income,etc.).

Indicator 404 may also include an indicator refresh rate property 648,which may include information that is used to determine how often system140 and/or client device 104 updates an account status indicator 404.Indicator refresh rate property 648 may be configured and appliedautomatically by system 140 when performing status notificationprocesses consistent with the disclosed embodiments. In another example,indicator refresh rate property 648 may be configured manually from user110 during a configuration process (e.g., configuration process 300A).In some embodiments, indicator refresh rate may depend on a certainamount of time (e.g., every ten minutes), a certain number oftransactions or item purchases (e.g., after the user purchases fiveitems), a certain amount of money spend (e.g., every $1,000, allpurchases over $3,000, etc.), and the like. For example, user 110 mayspecify she wishes the notification processes consistent with thedisclosed embodiments to check for an updated indicator status 644 everyfive minutes.

FIG. 7 illustrates a block diagram of exemplary data structures andrelationships consistent with the disclosed embodiments. FIG. 7 shows anexample of various aspects of how indicator rubrics 646 may generateindicator statuses 644 for indicators 404 associated with severalaccounts 620. FIG. 7 depicts an exemplary user associated with threeaccounts (e.g., a saving account, a checking account, and a student mealplan), each having their own balance calculation method 624. Forexample, in FIG. 7, the user may have elected to use the current balanceof her savings account for that account's parameter (e.g., actualaccount balance). The balance calculation method 624 for the user'schecking account and meal plans, however, may relate to other accountparameters, such as expenditures that provide an effective accountbalance parameter. The effective balance for the checking accountfurther contemplates expected monthly income.

Consistent with these exemplary settings, system 140 may determine thatthe account balance 626 for the savings account is $20,000 (e.g., thecurrent balance). Similarly, system 140 may determine the effectiveaccount balance for the checking account is 9,800 (e.g., $10,000 currentbalance+$5,000 income−$3,000 average expenses−$2,200 potentialpurchases). As an example, the disclosed embodiments may obtaininformation that is used to adjust the parameter status assigned to theaccounts for status notification. For example, the student meal planshown in FIG. 7 assumes there are, for example, two months left in thecurrent semester, although other aspects consistent with the disclosedembodiments may include any other relevant information from accountbalance data 626. The exemplary configuration of FIG. 7 also assumes theyearly allotment of meal plans for the user is 360 meals (resulting inthirty meals per month). Given a current balance of 100 meals, system140 may determine that the effective account balance for the meal planis 40 meals (100 current balance−2 months*30 meals/month).

In the example associated with FIG. 7, a single indicator 404 (Indicator1) is associated with the savings account and is a bar indicator(defined via indicator type 642). System 140 and/or client device 104may be configured to use account status Indicator 1's indicator rubric646 to determine to set the color of the account status bar indicator tored if the account balance (AB) of the savings account drops below$5,000. Otherwise, the system colors the bar green. In the illustratedexample, user account 1's balance exceeds $5,000, and thus the disclosedembodiments may set the indicator status 644 of the bar indicator togreen.

Further in the exemplary configuration of FIG. 7, Indicator 2 associateswith both user account 2 and account 3. In this example, Indicator 2takes the form of a glyph indicator (indicator type 642). UnderIndicator 2's indicator rubric 646, the glyph appears as a red “X” ifeither (1) the effective account balance of the checking account dropsbelow $10,000 or (2) the effective account balance of the meal plandrops below ten meals. In this example, while the effective accountbalance of the meal plan (account 3) exceeds ten meals, the effectiveaccount balance for the checking account (account 2) is below $10,000due in part to the potential purchases the user desires to make andidentified in the “potential transactions” entry. Thus, in this example,system 140 and/or client device 104 may determine based on indicatorrubric 646 that the appropriate glyph for indicator 2 comprises a red“X.”

The information reflected in arrangement 700 may be obtained and/ordetermined by system 140 and/or client device 104, or any other computersystem that performs processes consistent with the disclosedembodiments. The information, properties, etc. described in connectionwith arrangement 700 (and variations thereof) may be stored in one ormore memories, accessed by one or more processors, and used by the oneor more processors to perform processes consistent with the disclosedembodiments. Further, while FIG. 7 includes various exemplarycalculations and properties that may be used by the disclosedembodiments to determine the status of an account and the type ofrelevant account status indicator 644, the disclosed embodiments are notlimited to such configurations and relationships. Instead, the disclosedembodiments may implement other relationships and settings for providingaccount status indicators, may weigh other factors or information, mayobtain and use other inputs, different timeframes, and the like.

In some aspects, system 140 may enable user 110 to specify (e.g., thougha graphical user interface (GUI) presented by client device 104)threshold balances that facilitate system 140's determination ofindicator statuses (e.g., status 644) based on corresponding indicatorrubrics (e.g., rubric 644). In other embodiments, system 140 mayestablish a default threshold balance for accounts associated with oneor more of the account status indicators. For instance, a financialinstitution may require user 110 to maintain a minimum balance in achecking account to avoid transaction fees. In certain aspects, system140 may establish the required minimum balance as the default thresholdbalance for the checking account without requiring input from user 110.In further embodiments, system 140 may enable user 110 to establish a“window” that brackets a user-defined or default threshold balancevalues for purposes of determining the indicator statuses. For example,through the GUI presented by client device 104, user 110 may specify athreshold balance of $5,000 for user account 1 of FIG. 7, and may alsospecify a $250 window that brackets the threshold balance of $5,000.System 140 may, in some instances, establish a status of “green” for thebar indicator associated with user account 1 when the balance of useraccount 2 falls between $4,750 and $5,250.

In further aspects, the threshold balance specified by user 110 for aparticular account (e.g., through the GUI presented by client device104) may represent a budget established by the user over a correspondingtemporal period (e.g., a week, month, a holiday season, etc.). Forinstance, user 110 may establish a budget of $1,000 for charges on aparticular credit card account through the GUI presented by clientdevice 104. Using the disclosed embodiments, system 140 and/or clientdevice 104 may determine an indicator status based on a comparison ofthe recent charges on the credit card account against the establishbudget, and may generate and present to user 110 an account indicatorconsistent with the determined indicator status (e.g., a red bar whenspending exceeds the $1,000 budget or a green bar when spending fallsbelow the $1,000 budget).

Further, although described in terms of a savings account, a checkingaccount, and a student meal plan held by or associated with user 110,the data structures, relationships, and rubrics of FIG. 7 are notlimited to such exemplary types of accounts or number of accounts. Insome instances (not illustrated in FIG. 7), accounts 620 may alsoinclude a fourth user account associated with loyalty program in whichuser 110 participates. As described above, user 110 may elect, though agraphical user interface (GUI) presented by client device 104, a currentbalance of available rewards points as an account parameter associatedwith the loyalty program account. Based on user 110's input through theGUI, system 140 may establish a balance calculation method (e.g., method624) for the loyalty program account that accounts for a potential andrecurring transaction (e.g., potential transaction 626) in which user110 may exchange 1,000 loyalty points to obtain access to a streamingcontent service (e.g., Netflix™, etc.). System 140 may furtherestablish, based on user 110's input through the GUI, that user 110'sloyalty program account accrues an average of 1,500 points each month(e.g., income 626) based on purchase transactions at participatingretailers.

Furthermore, and as described above, system 140 may determine that user110's loyalty program account is associated with a current balance(e.g., balance 626) of 3,325 points, and may compute an effectiveaccount balance for user 110's loyalty program account of 3,385 points.In certain aspects, user 110 may, through the GUI, associate the loyaltyprogram account to an existing indicator (e.g., “Indicator 2” of FIG.7), and establish an rubric (e.g., indicator rubric 646) specifying thatthe glyph appears as a red “X” if either (1) the effective accountbalance of the checking account drops below $10,000, (2) the effectiveaccount balance of the meal plan drops below ten meals, or (3) theeffective account balance of the loyalty program account falls below1,000 points. User 110's linkage of the threshold loyalty point balanceof 1,000 points to Indicator 2 may, in some instances, ensure that user110's checking account includes funds sufficient to complete the monthlytransaction for the streaming content service in the event that theloyalty program account balance is insufficient to complete thetransaction. The disclosed embodiments are, however, not limited to suchexemplary links and associations, and in other embodiments, user 110 mayassociate the balance of the loyalty program account (or any otherparameters describing the loyalty program account) with user indicator 1or to any other existing indicator linked to other accounts 620.Further, in other aspects, user 110 may associate the balance of theloyalty program account to a new indicator and establish a correspondingindicator rubric.

In certain exemplary embodiments, client device 104 may be configured topresent icons that include multiple account status indicators associatedwith parameters of corresponding accounts. For example, client device104 may be configured to present, to user 110, a first account statusindicator 502 reflective of an account parameter of a first account anda second account status indicator 504 may reflect an account parameterof a second account within an icon (e.g., icon 402 of FIG. 4). In someaspects, client device 104 may configured to present account statusindicators 502 and 504 automatically without receiving input from user110 requesting presentation of account status indicators 502 and 504.

In further embodiments, system 140 and/or client device 104 may beconfigured to automatically generate, present, and/or modify one or moreof account status indicators 502 and 504 based on a current or priorgeographic position of user 110. For instance, and as described above,account status indicators 502 and 504 may be associated logical rules(e.g., notification rules) that establish a correspondence betweenpresentation statuses of account status indicators 502 and 504 (e.g., atype of indicator, visual, tactile, and/or audible characteristics ofthe indicator type, etc.) and one or more account parameters. In otheraspects, the notification rules may also specify particular geographicregions or locations associated with account status indicators 502 and504, and further, may establish the presentation statuses of accountstatus indicators 502 and 504 based on a current or prior geographicposition of user 110. The notification rules may also establish a linkbetween the current or prior geographic position of user 110 and ageneration, presentation, and/or modification of account statusindicators 502 and 504 by client device 104 and/or system 140.

For example, account status indicator 502 may reflect an actual oreffective account balance of a checking account held by user 110. Insome instances, a notification rule associated account status indicator502 may associate account status indicator 502 with geographic regionsthat include a shopping mall and other clusters of retail outletsregularly patronized by user 110. The indicator rubric may alsostipulate that client device 104 presents account status indicator 502to user 110 when a current geographic position of client device 104falls within the associated geographic regions or within a thresholddistance of the associated geographic regions.

Further, by way of example, account status indicator 504 may reflect aneffective balance of a transportation credit account that enables user110 to access modes of public transportation (e.g., bus, subway, train,etc.). In certain aspects, a notification rule for account statusindicator 504 may associate account status indicator 504 with geographicregions that include a train station, subway station, bus station, orother predetermined geographic locations at which user 110 may accesspublic transportation. As described above, the notification rule mayspecify that client device 104 presents account status indicator 504 touser 110 when a current geographic position of user 110 falls within orwithin a threshold distance of the associated geographic regions orlocations (e.g., client device 104 is disposed within subway station, orwithin 100 meters of the subway station).

In other embodiments, a device of a proximity system (e.g., an iBeacon™device) may be disposed within or near a train station, subway station,bus station, and/or an individual mode of public transportation (e.g.,at a point-of-sale (POS) terminal on a bus). Client device 104 may beconfigured to detect the proximity detection device, and in someaspects, the notification rule for account status indicator 504 mayspecify that client device 104 presents account status indicator 504 touser 110 in response to the detected proximity system device.

In some instances, system 140 may determine a current geographicposition of user 110 based on positional data received from clientdevice 104 (e.g., GPS data transmitted to system 140 from client device104 in response to a completed transaction, and/or a required update tosystem 140) or from a third-party system associated with client device104 (e.g., a mobile telecommunications provider). In certain aspects,system 140 may obtain the notification rules associated with accountstatus indicators 502 and 504. Based on a comparison of the currentgeographic position and the notification rules, system 140 may determinewhether to instruct client device 104 to present or modify apresentation of account status indicator 502 and/or account statusindicator 504. In other instances, client device 104 may determine thecurrent geographic position based on positional data obtained from theGPS, and may compare the current geographic position with thenotification rules of account status indicators 502 and 504. Based onthe comparison, client device 104 may determine whether to generate,present, and/or modify a presentation of account status indicator 502and account status indicator 504.

Further, in additional aspects, client device 104 may be configured todetect a proximity system device associated with one or more of accountstatus indicators 502 and 504 (e.g., an iBeacon™ device disposed on abus fundable by user 110's transportation credit account). By way ofexample, and responsive to the detected proximity system device, clientdevice 104 may be configured to generate, present, and/or modify apresentation of account status indicators 502 and/or account statusindicator 504 in accordance with the notification rules.

By way of example, system 140 may determine that client device 104 isdisposed within a shopping mall that, based on the correspondingnotification rule, would trigger a presentation or a modification ofaccount status indicator 502. In response to the determination, system140 may generate and transmit account status notification information toclient device 104 that instructs client device 104 to present accountstatus indicator 502 to user 110, or alternatively, to modify a portionof previously presented account status indicator 502. In other aspects,client device 104 may determine that its current geographic positionfalls within the shopping mall, and based on the notification rule,client device 104 may generate, present, and/or modify account statusindicator 502 to user 110 in accordance with account status notificationinformation received from system 140.

In further embodiments, system 140 (and additionally or alternatively,client device 104) may continue to monitor the geographic position ofclient device 104 and may determine that the user 110 is currently aportion of the shopping mall that includes a subway station. Thenotification rules may, for example, indicate that user 110's positionwithin the subway station triggers a presentation or modification ofaccount status indicator 504. Based on the notification rules, and usingprocesses consistent with the disclosed embodiments, system 140 maygenerate and transmit account status notification information to clientdevice 104 that instructs client device 104 to present account statusindicator 504 to user 110, or alternatively, to modify a portion ofpreviously presented account status indicator 504. Alternatively, clientdevice 104 may generate, present, and/or modify account status indicator504 to user 110 in accordance with account status notificationinformation received from system 140 and using processes consistent withthe disclosed embodiments. Account status indicator 504, as presented ormodified by client device 104, may indicate an effective balance of user110's transportation credit account that reflects a potential debit of asubway fare. Further, in some embodiments, client device 104 may presentor modify account status indicator 504 in response to the change ingeographic position without modifying a presentation of account statusindicator 502.

Through the disclosed embodiments, client device 104 may executesoftware processes that present account status indicators to user 110based on a correspondence between a current geographic position ofclient device 104 and geographic regions or locations linked to theaccount status indicators. In certain aspects, client device 104 maypresent a graphical user interface (GUI) that enables user 110 toestablish a link between a specific geographic region and one or more ofthe account status indicators. Client device 104 may store informationassociated with the established link to define portions of thenotification rules for the account status indicators, and additionallyor alternatively, may transmit the information across network 120 tosystem 140, which may generate the corresponding portions of thenotification rules.

In other aspects, system 140 may execute software instructions thatestablish associations between account status indicators andcorresponding geographic regions without input from user 110. Forexample, system 140 may identify an account status indicator associatedwith a credit card account held by user 110. In some instances, system140 may access transaction data identifying purchase transactionsinvolving the credit card account (e.g., within stored transaction data144C), may identify retailers associated with the purchase transactions,and further, may determine geographic locations of the identifiedretailers. System 140 may, for example, link the determined geographiclocations to the account status indicator associated with a credit cardaccount, and additionally or alternatively, link geographic regions thatinclude clusters of the determined geographic locations the accountstatus indicator associated with a credit card account. As describedabove, the linkage of the geographic regions and locations to theaccount status indicator may define at least a portion of thenotification rule associated with the credit card account indicator.

Further, by way of example, system 140 may identify an account statusindicator corresponding to an account associated with a loyalty programin which user 110 participates. The loyalty program may, for example, besponsored by a merchant, and system 140 may obtain informationidentifying the particular loyalty program account (e.g., accountnumber, points balance, etc.) from a corresponding data repository(e.g., stored account data 144B). In some instances, system 140 mayidentify geographic positions of retail locations of the merchant, andmay associate the identified geographic positions to the account statusindicator associated with a loyalty program account. The associationbetween of the geographic regions and locations to the account statusindicator may define at least a portion of the notification ruleassociated with the loyalty program account indicator.

Through the disclosed embodiments, system 140 and/or client device 104may selectively generate, present, and/or modify account statusindicators based on detected changes in user 110's current geographicposition. In additional aspects, system 140 and/or client device 140 maybe configured to selectively modify an account type associated with theindicator based on a geographic location of user 110.

By way of example, user 110 may hold a checking account issued by afinancial institution (e.g., business entity 160), may participate in aloyalty program sponsored by a merchant having multiple retaillocations, and may hold a transportation credit account loaded withfunds or tokens facilitating a use of public transportation. In anembodiment, a notification associated with an account status indicatormay be associated with a default account type (e.g., user 110's checkingaccount), and system 140 and/or client device 104 may be configured tomodify the default account type based on user 110's current geographicposition and in accordance with the notification rules.

For instance, the notification rules may establish the loyalty programaccount as the account type for the account status indicator when user110's current geographic position falls within a threshold distance of aretailer location of the merchant. Further, by way of example, thenotification rules may establish the transportation credit account typeas the account type for the account status indicator when user 110'scurrent geographic position falls within the threshold distance of asubway or bus station (or in response to a detection of a proximitysystem device associated with subway or bus station). In certainaspects, user 110 may establish portions of the notification rules(e.g., threshold distances or geographic region) through a correspondingGUI presented by client device 104, or system 140 may establish portionsof the notification rules programmatically and without input from user110 (e.g., based on a geographic analysis of prior purchasetransactions).

By way of example, system 140 may receive positional data from clientdevice 104, and may determine that a current geographic position of user110 falls within the threshold distance of a retail location of amerchant that sponsors user 110's loyalty program account. In responseto the determination, system 140 may transmit data associated with theloyalty program account to client device 104, which modify the accountstatus indicator to present data associated with the loyalty programaccount in accordance with the notification rules and using processesconsistent with the disclosed embodiments. In some instances, themodified account status indicator may include a modification of a color,shape, or other visual characteristic, which indicates to user 110 thatthe account status indicator reflects an account parameter of theloyalty program account.

Further, in some instances, system 140 may receive additional positionaldata that indicates user 110's current geographic position falls withinthe threshold distance of a subway station. In response to the change inuser 110's current geographic position, system 140 may transmit dataassociated with the transportation credit account to client device 104,which may modify the account data indicator to present data associatedwith transportation credit account in accordance with the notificationrules and using processes consistent with the disclosed embodiments. Forexample, the modified account status indicator may indicate an effectivebalance of the transportation credit account that reflects a potentialdebit of a subway fare. By way of example, the presented account statusindicator may modify a color, shape, or other visual characteristic thatrenders the account status indicator specific to the transportationcredit account.

Furthermore, if system 140 were to determine that user 110's currentgeographic position falls outside of the threshold distance of eitherthe subway station or the retail locations, system 140 may transmit dataassociated with the default checking account to client device 104. Insome aspects, the transmitted data may instruct client device 104 tomodify the account status indicator to present data indicative of astatus (e.g., a balance) of the default checking account.

In other embodiments, the notification rules may define other parametersof an account status indicator (e.g., a type of balance (effective oractual), a type of indicator (glyph, bar, pie chart, etc.) and/or avisual, tactile, or audible characteristic of the indicator, etc.) basedon a geographic location of user 110. In one aspect, the notificationrules for the account status indicator may establish a bar indicator(e.g., indicators 502 or 504 of FIG. 5A) as a default indicator type,and may define a modification of the default indicator type to a glyph(e.g., FIG. 5D) or a solid-color indicator (e.g., FIG. 5C) when user110's geographic position falls within a specific geographic region orregions. By way of example, user 110 may regularly purchase goods andservices in crowded areas (e.g., stadiums, etc.), and the notificationrules may require client device 104 (or system 140) to display asolid-color indicator when user 110 is disposed within the stadium. Incertain instances, client device 104's modification of the default barindicator to a solid color indicator may continue to provide user 110with non-obtrusive information identifying a status of an accountwithout disclosing details regarding magnitudes and values of accountparameters, such as account balance or credit limits.

In additional embodiments, system 140 and/or client device 104 maymodify a type of balance associated with a presented account statusindicator based on a current geographic position of user 110. Forinstance, the notification rules may establish an actual or effectivebalance as a default account parameter for an account status indicatorassociated with a credit card account held by user 110. The notificationrules may further specify a remaining amount of available credit as theaccount parameter of the account status indicator when user 110 isdisposed within a geographic region having a concentration of merchants(e.g., a shopping mall). In certain instances, system 140 may determinethat user 110's current geographic position falls within the shoppingmall, and may transmit credit card account data instructing clientdevice 104 to modify the presented account data to reflect not theactual or effective account balance of the credit card account, butinstead the remaining amount of available credit for the credit cardaccount. In certain aspects, the presented account status indicator maymodify a color, shape, or other visual, tactile, or audiblecharacteristic of the indicator to enable user 110 to readily perceivethe modified balance type.

In the embodiments disclosed above, reference is made to icons thatinclude one or more account status indicators (e.g., account statusindicators 502 and 504). The disclosed embodiments are, however, notlimited to the presentation and modification of two account statusindicators, and in other embodiments, system 140 and/or client device104 may selectively generate, present, and/or modify any additional oralternate numbers and types of account status indicators appropriate forpresentation by client device 104.

In certain embodiments, client device 104 may represent a computingdevice having a display unit capable of presenting one or more accountstatus indicators within an augmented reality (AR) interface presentedto a user. For example, client device 104 may represent “smart glasses”that include an optical head-mounted display (OHMD) configured topresent interface elements as an AR view that “pop-ups” within a fieldof view of user 110 and modifies a visual appearance of an object withinuser 110's field-of-view (or within a presented image or video) toreflect a status of one or more accounts of user 110. The smart glassesmay, in some instances, communicate with system 140 across network 120,and may be configured to receive account status notification informationfrom system 140 at predetermined intervals, based on a geographiclocation of user 110, and/or in response to predetermined triggeringevents established by user 110 or system 140 (e.g., a potential purchaseof a product or service, a change in a status of one or more of user110's accounts detected by system 140). In response to the receivedaccount status notification information, and in accordance withnotification rules established by user 110 and/or system 140, the smartglasses may generate instructions that cause the OHMD to present one ormore corresponding account status indicators within user 110'sfield-of-view, and additionally or alternatively, to modify visualcharacteristics of one or more previously presented account statusindicators to reflect updates or changes in corresponding accounts heldby user 110.

The disclosed embodiments are, however, not limited to client deviceshaving OHMDs capable of displaying interface elements within user 110'sfield-of-view, and in other embodiments, client device 104 may include anon head-mounted device configured to generate a “head-up” display thatprojects one or more interface elements within user 110's field of view.For instance, client device 104 may represent a vehicle-based computingdevice having a display unit that projects interface elements onto aninterior portion of a windshield of user 110's vehicle. Thevehicle-based computing device may be in communication with system 140via network 120, and additionally or alternatively, may be incommunication with a mobile communications device of user 110 using aBluetooth™ connection, a NFC connection, or other appropriatecommunications protocol. In certain aspects, the vehicle-based computingdevice may receive account status notification information (e.g.,directly from system 140 over communication network 120 or indirectlythrough user 110's mobile communications device) and may generateinstructions that cause the display unit to project one or morecorresponding account status indicators within user 110's field-of-view,and additionally or alternatively, to modify visual characteristics ofone or more previously presented account status indicators to reflectupdates or changes in corresponding accounts held by user 110.

For example, using the exemplary techniques described above, user 110may associate a glyph indicator (e.g., the indicator of FIG. 5D) with aneffective account balance of user 110's checking account and with aneffective account balance of user 110's loyalty program account. Thedisclosed embodiments may also enable user 110 to establish (e.g., usinga graphical user interface (GUI) presented by client device 104) anindicator rubric specifying that the glyph indicator appears as a red“X” if either (1) the effective account balance of the checking accountdrops below $10,000 or (2) the effective account balance of the loyaltyprogram account falls below 1,000 points. Furthermore, user 110 mayconfigure notification processes consistent with the disclosedembodiments to check for an updated indicator status at specifiedtemporal intervals (e.g., every five minutes), in response to a purchaseof a product or service using the checking account (e.g., using a debitcard linked to user 110's checking account), or in response to a changein a point balance of user 110's loyalty program account (e.g., apurchase transaction that accrues loyalty points, or a transaction inwhich user 110 exchanges loyalty program points for a product orservice).

In one instance, after the specified temporal interval, system 140 mayaccess stored account data associated with user 110's checking accountand user 110's loyalty program account (e.g., within account data 144B),and may determine that the effective account balance of user 110'schecking account is $11,375, and that the effective account balance ofuser 110's loyalty program account is 1,100 points. Applying theestablished indicator rubric to the effective account balances, system140 may determine that client device 104 should present a green “checkmark” as the glyph indicator (e.g., that the indicator status is that ofa green check mark). System 140 may also generate account statusnotification information that identifies the indicator type (e.g.,glyph) and specifies the indicator status (e.g., green check mark). Insome instances, the account status notification may also includeinformation identifying the checking account and/or loyalty programaccount (e.g., account numbers, names of issuing financial institutionor retailers, etc.), and further, information identifying the effectiveaccount balances of the checking account and/or the loyalty programaccounts. System 140 may be configured to transmit the account statusnotification information to client device 104 across network 120 usingany of the communications protocols outlined above.

In some embodiments, client device 104 (e.g., a pair of smart glasses)may include an OHMD configured to present one or more account statusindicators as an AR view that “pop-ups” within a field of view of user110 and modifies a visual appearance of an object within user 110'sfield-of-view (and/or within an image or video presented by the OHMD) toreflect a status of one or more accounts of user 110. Client device 104may, in certain aspects, be configured to receive the account statusnotification information from system 140, generate an account statusindicator in accordance with the account status notificationinformation, and instruct the OHMD to render the generated accountstatus indicator for presentation to user 110 at a correspondingposition within the field-of-view of user 110, as illustrated in FIG.8A.

FIG. 8A schematically illustrates an exemplary field-of-view 800provided by an exemplary pair of smart glasses having an OHMD. Incertain aspects, the smart glasses (e.g., client device 104) may receivethe account status notification information from client device 104(e.g., specifying a glyph indicator having as green check mark), and maygenerate the specified glyph indicator for rendering and presentationwithin field-of-view 800. By way of example, as illustrated in FIG. 8A,client device 104 may instruct the OHMD to present glyph indicator 812within an upper-left corner of field-of-view 800. In some aspects, asize and/or a position of glyph indicator 814 within field-of-view 800may be established by user 110 (e.g., within corresponding notificationrules using a GUI presented by client device 104), and additionally oralternatively, by client device 104 or system 140 based on operationalparameters and limitations of the OHMD.

Further, as described above, system 140 may be configured to monitortransaction data associated with user 110's checking account, and insome aspects, system 140 may detect that, e.g., a hotel in Toronto,Canada, placed a hold of $2,000 on user 110's checking account. Inresponse to the detected transaction, system 140 may determine that theeffective account balance of user 110's checking account is currently$9,375 (i.e., below the $10,000 threshold). In certain aspects, andbased on the corresponding notification rules and/or indicator rubrics,system 140 may determine to modify the indicator status for the glyphindicator to correspond to a red “X,” and transmit updated accountstatus notification information to client device 104. As describedabove, the updated account status notification information may includethe modified indicator status, and additionally or alternatively,information identifying the modified effective account balance of user110's checking account.

Client device 104 may receive the updated account status notificationinformation, and using the exemplary techniques described above, mayinstruct the OHMD to render and present a modified account statusindicator consistent with the changed status of user 110's checkingaccount. For example, as outlined in FIG. 8B, client device 104 mayinstruct the OHMD to present to user 110 a modified account statusindicator 822 in the form of a red “X,” which indicates to user 110 thatthe effective account balance of the checking account has fallen belowthe user-specified threshold balance. In certain aspects, themodification to the account indicator, which the OHMD presents withinuser 110's field-of-vision, may act as a reminder that user 110 shouldconsider alternate forms of payment that do not immediately impact user110's checking account, or alternatively, that user 110 should top offthe checking account with reserve funds in order to maintain the desiredthreshold balance.

Furthermore, as described above, the disclosed embodiments may beconfigured to present visual, audible, and/or tactile indicators thatreflect an impact of a potential purchase of a product or service on oneor more accounts held by user 110. By way of example, user 110 may weara pair of “smart glasses” that include an OHMD (e.g., client device104), and user 110 may browse products offered for sale by a retailer ofconsumer electronics. In certain aspects, client device 104 may modifyan appearance of at least a portion of a product disposed within user110's field-of-view (e.g., the field-of-view defined by user 110's smartglasses) to reflect a status of one or more financial services accountsand loyalty program accounts held by user 110.

By way of example, user 110 may browse products offered for sale by amerchant of consumer electronics. In certain instances, and asillustrated in FIG. 9A, user 110 may view a portion of a tablet computer(e.g., tablet computer portion 900) through a correspondingfield-of-view 800 of user 110's smart glasses. In FIG. 9A, user 110 mayview information 902 identifying a model of the tablet computer (e.g.,an iPad Air™) and a configuration of the tablet computer (e.g., 128 GBof storage). User 110 may also view a label 904 affixed to tabletcomputer portion 900 that includes a machine-readable code 904A and alist price 904B of the tablet computer (e.g., $699). In some aspects,machine-readable code 904A may correspond to an optical machine-readablerepresentation of data identifying the tablet computer, characteristicsof the tablet computer (e.g., list price, etc.), and/or the merchantthat offers the tablet computer for sale. For example, machine-readablecode 904A may include, but is not limited to, a bar code, a QR code, andother one- and two-dimensional optical machine-readable codes.

In some aspects, client device 104 (e.g., the smart glasses having theOHMD) may execute software processes that cause a digital cameraassociated with client device 104 to capture an image of tablet computerportion 900. Client device 104 may, for instance, perform opticalcharacter-recognition (OCR) processes on the captured image data toobtain product information, which includes, but is not limited to, thetablet model (e.g., iPad Air™), the tablet configuration (e.g., 128 GB),and the tablet price (e.g., $699). In other instances, client device 104may process the captured image data in order to obtain product and/orretailer information encoded within machine-readable code 904B. By wayof example, the obtained product and/or merchant information mayinclude, but is not limited to, a Universal Product Code (UPC) numberassociated with the tablet computer, a model, configuration, and/orprice of the tablet computer, or the merchant offering the tabletcomputer for sale.

In an embodiment, the digital camera associated with client device 104may be configured to capture the image data of tablet computer portion900 automatically and without input from user 110. For example, thedigital camera may continuously obtain image data corresponding totablet computer portion 900, and client device 104 may execute softwareprocesses that automatically capture and store a portion of the obtainedimage data having image characteristics (e.g., image focus, imageresolution, etc.) sufficient for OCR and code processing, as describedabove. In other aspects, however, client device 104 may capture andstore a portion of the obtained image data based on user input, e.g., agestural input, a verbal input, or other appropriate input appropriateto client device 104.

In some aspects, client device 104 may be configured to transmit theobtained product and/or merchant information to system 140, which mayprocess the received information to determine an impact of user 110'spotential purchase on one or more of user 110's accounts. The disclosedembodiments are, however, not limited to exemplary processes in whichclient device 104 performs OCR and code-reading processes on capturedimage data. In other instances, client device 104 may be configured totransmit the captured image data to system 140, which may perform theOCR and/or code-reading processes to generate information identifyingthe tablet computer and additionally or alternatively, the merchantoffering the tablet computer for sale, using any of the techniquesdescribed above.

In certain aspects, system 140 may be configured to identify and obtainadditional product and/or merchant information necessary to determine animpact of the potential purchase on user 110's accounts. By way ofexample, the received product information may include a UPC numberassociated with the tablet computer and information identifying themerchant that offers the tablet computer for sale, but may not include aprice of the tablet computer. In some instances, system 140 may beconfigured to query an additional computing system associated with themerchant (e.g., across network 120 through a corresponding API), and inresponse to the query, system 140 may receive the price of the tabletfrom the merchant system.

Further, in some embodiments, system 140 may execute software processesthat assess an impact of the potential purchase of the tablet computeron one or more accounts held by user 110. By way of example, user 110and/or system 140 may establish notification rules and/or indicatorrubrics using any of the exemplary processes outlined above, whichsystem 140 may store in a corresponding data repository (e.g., datarepository 144). In certain aspects, system 140 may retrieve the storednotification rules and/or indicator rubrics associated with user 110,and may determine that one of the retrieved notification rules requiresthat client device 104 modify an appearance of a product in user 110'sfield-of-view whose purchase is deemed eligible for loyalty points. Forexample, the notification rule may specify that client device 104 notifyuser 110 of the tablet computer's eligibility for loyalty points bypresenting a blue ring or halo that surrounds the tablet computer withinuser 110's field-of-view (e.g., field-of-view 800 of user 110's smartglasses in FIG. 9A).

In response to the notification rule and the determined eligibility ofthe tablet computer for loyalty points, system 104 may generate accountstatus notification information that identifies the eligibility of thetable computer for loyalty points, and further, instructs client device104 to present the blue ring or halo surrounding the table computerwithin user 110's field-of-view. System 140 may, for example, transmitthe generated account status information to client device 104 acrossnetwork 120 using any of the communications protocols outlined above.

Client device 104 may be configured to receive the account statusnotification information from system 140, and may execute softwareprocesses that generate and present an interface element within user110's field-of-view that surrounds the table computer with the blue ringor halo. For instance, as illustrated in FIG. 9B, client device 104 mayinstruct the OHMD to present an interface element 912 within user 110'sfield-of-view in a manner that surrounds tablet computer portion 900,and further, to color interface element 912 blue within field-of-view800. In some aspects, the OHMD may present ring 912 as an augmentedreality (AR) view that “pop-ups” within the field-of-view of user 110and modifies a visual appearance of an object within user 110'sfield-of-view (or within a presented image or video) to reflect a statusof one or more accounts of user 110.

In some embodiments, client device 104 may execute software processesthat generate an interface element corresponding to ring 912, which theOHMD may render and present within user 110's field-of-view 800. Forexample, as described above, the digital camera associated with clientdevice 104 may continuously sample image data from user 110'sfield-of-view, and using one or more image processing techniques, clientdevice 104 may establish a boundary of the visible portion of the tabletcomputer within the sampled image data, and further, may determine acentroid of the portion of user 110's field-of-view enclosed by theboundary (e.g., the centroid of the visible portion of the tablecomputer). In some aspects, the interface element corresponding to ring912 of FIG. 9B may be generated initially as a two-dimensional circularelement centered on the determined centroid of the visible portion ofthe tablet computer, with the portion of the circular element enclosedwithin the determined boundary eliminated. The dimensions of the ring912 may, in some instances, be established by user 110 within thecorresponding notification rule (e.g., using any of the processesdescribed above), or alternatively, may be established by client device104 and/or system 140 based on one or more properties of the OHMD or adimension of field-of-view 800.

In other embodiments, system 140 may determine that the notificationrules and/or indicator rubrics associated with user 110 require clientdevice 104 to modify an appearance of a product within user 110'sfield-of-view to reflect an impact of a potential purchase of theproduct on one or more accounts held by user 110. For instance,notification rules consistent with the disclosed embodiments may specifythat client device 104 notify user 110 of the impact of the potentialpurchase of the tablet computer on user 110's checking account, creditcard account, and loyalty program account by presenting correspondingaccount status indicators within user 110's field-of-view.

In certain aspects, the account status indicators may representconcentric rings disposed about the tablet computer within user 110'sfield-of-view, and the concentric ring indicators may visuallycharacterize the impact of user 110's potential purchase of the tablecomputer on effective account balances of corresponding ones of user110's checking account (e.g., a through a purchase using a linked debitcard), user 110's credit card account (e.g., a Visa™ card), and user110's loyalty program account. Further, client device 104 maycharacterize the status of actual or effective account balances of thechecking, credit card, and loyalty program accounts by establishingand/or varying one or more visual characteristics of the concentric ringindicators (e.g., a color, color gradient, or pattern) based on acorresponding indicator rubric or notification rule established usingany of the techniques outlined above.

By way of example, system 140 may obtain notification rules and/orindicator rubrics that associate a first concentric ring indicator withthe effective balance of user 110's checking account, that associate asecond concentric ring indicator (e.g., disposed proximate to an outercircumference of the first concentric ring indicator) with the effectivebalance of user 110's credit card account, and further, that associate athird concentric ring indicator (e.g., disposed proximate to an outercircumference of the second concentric ring indicator) with an actualbalance of user 110's loyalty program account. In further aspects, anindicator rubric obtained by system 140 may specify that the firstconcentric ring indicator appear as red when the effective balance ofuser 110's checking account drops below a $10,000 threshold, or greenwhen the effective balance remains about the $10,000 threshold.Additionally, indicator rubrics consistent with the disclosedembodiments may specify that the third concentric ring indicator appearsas red when the actual balance of user 110's loyalty program accountremains below a 10,000-point threshold associated with a $100 cashreward, and as green when the actual balance exceeds the 10,000-pointthreshold. Finally, an indicator rubric obtained by system 140 mayspecify that the second concentric ring indicator appear as green whenan effective account balance of user 110's credit card account, whenadjusted to account for a cash reward from user 110's loyalty program,remains below a $5,000 threshold, or red when the adjusted effectiveaccount balance rises above the $5,000 threshold. In certain instances,user 110 and/or system 140 may establish portions of one or more of thenotification rules and/or indicator rubrics using any of the exemplarytechniques outlined above.

In certain aspects, using any of the exemplary techniques identifiedabove, system 140 may determine that user 110's checking account isassociated with a current effective account balance of $10,250, thatuser 110's credit card is associated with a current effective balance of$4,350, and that user 110's loyalty program account is associated withan actual balance of 9,885 points. Further, the received and/orgenerated product information may indicate a cost of $699 for user 110'spotential purchase of the tablet computer. Applying the notificationrules and/or indicator rubric to user 110's checking account, system 140may determine that the purchase of the tablet computer would reduce theeffective account balance of user 110's checking account to $9,551, andthat the first concentric ring indicator should appear red whenpresented by client device 104.

Based on stored loyalty program information (e.g., information stored inaccount data 144B that specifies the loyalty program accrues one pointfor each dollar sent), system 140 would determine that the purchase ofthe tablet computer would result in an actual loyalty point balance of10,257 points, which would provide user 110 with a $100 cash reward.System 140 may, in some instances, determine that the third concentricring indicator should appear green when presented to user 110 by clientdevice 104.

Further, applying the notification rules and/or indicator rubric to user110's credit card account, system 140 may determine that the $100 cashreward issued by user 110's loyalty program offsets the purchase priceof the tablet computer, which would increase the effective balance ofuser 110's credit card account to $4,949. In certain aspects, system 140may determine that the second concentric ring indicator should appeargreen when presented to user 110 by client device 104.

In some embodiments, system 140 may generate account status notificationinformation that specifies the presentation of the first, second, andthird concentric ring indicators (e.g., corresponding, respectively, toan effective balance of user 110's checking account, an effectivebalance of user 110's credit card account, and an actual balance of user110's loyalty program account), and further, includes informationidentifying the status (e.g., red or green) of the concentric ringindicators. In some aspects, the generated account status notificationinformation may further identify the effective balance of user 110'schecking account, the effective balance of user 110's credit cardaccount, and/or the actual balance of user 110's loyalty program accountthat would result from the potential purchase of the tablet computer,and additionally or alternatively, the $100 cash reward obtained fromthe potential purchase of the tablet computer. System 140 may beconfigured to transmit the generated account status notificationinformation to client device 104 across network 120 using any of thecommunications protocols outlined above.

Client device 104 may be configured to receive the account statusnotification information from system 140, and may execute softwareprocesses that generate and present the first, second, and thirdconcentric ring indicators as interface elements that surround theportion of the tablet computer visible within user 110's field of view.For example, client device 104 may execute software processes thatgenerate the interface elements corresponding to the first, second, andthird concentric ring indicators using any of the exemplary techniquesdescribed above, and the OHMD may render the generated interfaceelements for presentation within user 110's field of view.

FIG. 9C illustrates an exemplary augmented reality (AR) view presentedby client device 104 within user 110's field-of-view 800, in accordancewith disclosed embodiments. For instance, as illustrated in FIG. 9C,client device 104 may instruct the OHMD to render and present a redinterface element 922 corresponding to the first concentric ringindicator and indicative of an impact of the potential purchase of thetablet computer on the effective balance of user 110's checking account.Further, for example, client device 104 may instruct the OHMD to presentgreen interface elements 924 and 926 that correspond, respectively, thesecond and third concentric ring indicators (which indicate the impactof the potential purchase of the table computer on the effective balanceof respective ones of user 110's credit card account and on user 110'sloyalty program account). In some embodiments, the OHMD may presentinterface elements 922, 924, and 926 an augmented reality (AR) view that“pop-ups” within the field-of-view 800 and surrounds the visible portion900 of the tablet computer within field-of-view 800. In certain aspects,interface elements 922, 924, and 926 may modify an appearance of visibleportion 900 of the tablet computer (e.g., as perceived by user 110) toindicate to user 110 an impact of the potential purchase of the tabletcomputer on the effective balance of user 110's checking account, creditcard account, and loyalty program account.

In certain aspects, by viewing interface elements 922, 924, and 926within field-of-view 800, user 110 may readily determine an impact ofthe potential purchase of the tablet computer on the checking account,credit card account, and loyalty account. For instance, as interfaceelement 924 is colored green, user 110 may determine that the purchaseof the tablet computer would not increase the effective balance of thecredit card account beyond the threshold specified in the correspondingnotification rule and/or indictor rubric. Further, since the OHMDpresents interface element 926 as green, user 110 may determine that thepurchase of the laptop would entitle user 110 to a cash reward of $100(e.g., based on a potential increase in loyalty points above the 10,000threshold established by user 110).

Further, the disclosed embodiments also enable user 110 to link (e.g.,through a corresponding GUI presented by client device 104) anyadditional or alternate numbers and types of accounts to concentric ringindicators forming portions of the AR view presented by the OHMD. Incertain aspects, user 110's ability to “layer” multiple ring indicatorslinked to status of corresponding account parameters, and to filter thelayered ring indicators adaptively and dynamically using the GUI, mayassist the user 110 in making an optimal decision regarding not only apotential purchase, but also the account or accounts impacted by thepurchase.

The disclosed embodiments are, however, not limited to an optical device(e.g., the OHMD of client device 104) that generates and presentsinterface elements within an AR view that modifies a visual appearanceof a physical object disposed within user 110's field-of-view (e.g.,portion 900 of the tablet computer). In other embodiments, the opticaldevice (e.g., the OHMD or a device capable of generating a “heads-up”display) may be configured to present to user 110 multimedia content(e.g., stored or streaming digital image or digital video content)within user 110's field of view. In certain aspects, the OHMD may beconfigured to generate and present interface elements that modify anappearance of an object within the presented multimedia content (e.g.,as perceived by the user) to reflect a status of one or more accounts ofuser 110. For instances, client device 104 may instruct the OHMD topresent one or more of interface elements 922, 924, and 926 within user110's field-of-view to modify a visual appearance of an object orindividual within the presented multimedia content and convey a statusof user 110's checking account, credit card account and/or loyaltyprogram account.

Further, the disclosed embodiments may enable client device 104 of user110 to receive account status notification information from system 110,and based on the received information, to generate and present to user110 one or more graphical, tactile, or audible indicators reflective ofa status of parameters of one or more accounts held by user 110. In someaspects, the presented indicators may include information identifying arelationship of an account parameter (e.g., an effective accountbalance) to a user-defined or default threshold, and further, mayindicate a particular value associated with the account parameter. Asdescribed above, indicators consistent with the disclosed embodimentsmay include, but are not limited to, colored status bar indicators,glyph indicators, symbol indicators, picture indicators, and concentricring indicators.

In certain instances, the account status indicators generated andpresented by client device 104 may indicate a status of an accountparameter, such an effective account balance or a loyalty point balance,relative to a user- or system-established threshold. For example, aglyph indicator may correspond to a green “check mark” when an effectiveaccount balance of user 110's checking account exceeds a thresholdbalance, or alternatively, a red “X” when the effective account balancefalls below the threshold balance. In other aspects, and in additionalto reflecting a relationship between the account parameter and theestablished threshold, the generated and presented account statusindicator may also indicate to user 110 the actual value of the accountparameter. For example, client device 104 may generate and present touser 110 a status bar indicator that is not only shaded red or greendepending on the relationship between an effective account balance ofuser 110's checking account and an established threshold, but also takesthe form of a bar graph that presents to user 110 a current value of theeffective account balance. In one embodiment, user 110 may associate aparticular type of account status indicator with a corresponding accountin a notification rule and/or indicator rubric using any of theexemplary techniques described above. In other instances, system 140 mayassign default types of account status indicators (e.g., lessdescriptive glyph indicators) to corresponding ones of user 110'saccounts without input from user 110.

The disclosed embodiments may also enable client device 104 to receiveaccount status notification information from system 140, and to transmitthe received information to one or more additional devices (e.g.,“connected” devices) that are capable of establishing communicationsessions with client device 104 and capable of displaying account statusindicators of varying detail and complexity. By way of example,communications between client device 104 and the connected devices mayoccur across network 120 (e.g., a wired or wireless LAN, a RF network, aNFC network, a WiFi network, a Bluetooth™ network) using any of thecommunications protocols outlined above.

In certain aspects, client device 104 may execute software processesthat receive account status notification information from system 140,that identify one or more of the connected devices eligible to receivenotifications and present indicators (e.g., based on previouslyestablished connected device information), and further, thatautomatically transmit or “push” portions of the received notificationinformation to the eligible connected devices without input orintervention from user 110. In some instances, client device 104 mayselect portions of the received notification information fortransmission to the connected devices, or may modify portions of thereceived information, to comport with corresponding capabilities andfunctionalities of the connected devices, which may be set forth in thepreviously established connected device information.

In some aspects, user 110 may, through a graphical user interlace (GUI)presented by client device 104, establish portions of the connecteddevice information that identify one or more connected devices capableof establishing communications with client device 104, identify whetherthe connected devices are eligible to receive notification informationand present indicators, and further, identify a type of accountindicator the eligible connected devices may present to user 110. In oneembodiment, user 110 may establish the connected device informationusing techniques similar to those outlined above that establishnotification rules and/or indicator rubrics. In other embodiments,system 140 and/or client device 104 may establish, without user input orintervention, at least a portion of the connected device information byassociating corresponding connected devices with default indicator typesfor specific accounts. In certain aspects, client device 104 may storethe established connected device information in a data structure withina corresponding local data storage, or may periodically upload theestablished connected device information for storage in a datarepository locally accessible to system 140 (e.g., data repository 144).

FIG. 10 illustrates and exemplary tabular data structure 1000 withinwhich client device 140 may store established connected deviceinformation, in accordance with disclosed embodiments. For example, andas described above, client device 104 may present to user 110 agraphical user interface (GUI) that enable user 110 to identify one ormore connected devices capable of establishing communications sessionswith client device 104, and further, to establish correspondingnotification parameters for the identified connected devices. Clientdevice 104 may, in some instances, propose a set of candidate connecteddevices that previously established communications sessions with clientdevice 104 (e.g., a computing device disposed within user 110's MiniCooper™ and with which client device 104 previously coupled andestablished communications sessions) or alternatively, that are capableof establishing a communications session with client device acrossnetwork 120 (e.g., based on a response to a broadcast query message).

In certain aspects, the GUI may allow user 110 to establish one or morenotification parameters for the connected devices identified by clientdevice 104. As outlined in FIG. 10, notification parameters consistentwith the disclosed embodiments include, but are not limited to, a devicename, a device address, an eligibility parameter, an access typeparameter, and an indicator type parameter. Upon specification of thenotification parameters for the corresponding connected devices, clientdevice 104 may generate data records for the corresponding devices,which may be incorporated into and stored within data structure 1000. Insome instances, user 110 may specify values for the notificationparameters within the GUI for one or more of the connected devices. Inother instances, however, client device 104 may establish or suggestvalues appropriate to notification parameters for one or more of theconnected devices (e.g., devices names that comport with system orcommunications protocol requirement, or addresses identifiedprogrammatically by client device 104), and user 110 may be invited bythe GUI to confirm the established or suggested values.

For example, in FIG. 10, data record 1002 corresponds to a computingdevice disposed within user 110's Mini Cooper™ vehicle (e.g., the“connected” Mini Cooper™). In certain aspects, client device 104 mayestablish a device address for the connected Mini Cooper™ (e.g.xx:xa:95:xd:68:16). Further, by way of example, user 110 may specifywithin the GUI that the connected Mini Cooper™ device is eligible toreceive notifications, and further, that the connected Mini Cooper™should be afforded an “Authenticated” type of access to user 110'saccount information. In certain aspects, user 110's establishment of“Authenticated” access for the connected Mini Cooper™ implies thataccount status notification information provided to the connected MiniCooper™ may include not only information that identifies a relationshipbetween an account parameter and an established threshold (e.g., whetheran effective balance of user 110's checking account exceeds a thresholdvalue), but also information that identifies the value of the effectivebalance (e.g., user 110's checking account includes an effective balanceof $11,500, which exceeds the threshold of $10,000). Further, user 110'sability to establish the “Authenticated” access for the connected MiniCooper™ may be based on an ability of client device 140 to communicatesecurely with the connected Mini Cooper™ across communications network120. Further, as illustrated in FIG. 10, the connected Mini Cooper™ maybe capable of generating and presenting status bar indicators, pie chartindicators, background color indicators, picture indicators, symbolindicators, glyph indicators, text-based indicators, and/or auditoryindicators.

Referring back to FIG. 10, data record 1004 corresponds to a connectedlighting system capable of communicating with client device 104 overnetwork 120. As described above, client device 104 may establish adevice address for the connected lighting system (e.g.,xx:yb:90:xe:47:15), and user 110 may specify within the GUI thatconnected lighting system is eligible to receive account statusnotifications. User 110 may also specify within the GUI that theconnected lighting system is afforded “Indirect” access to user 110'saccount information, and further, that the connected lighting system iscapable of presenting only a background color account status indicatorto user 110. In certain aspects, user 110's establishment of “Indirect”access for the connected lighting system implies that account statusnotification information communicated from client device 104 to theconnected lighting system may only identify a relationship between anaccount parameter and an established threshold (e.g., whether aneffective balance of user 110's checking account exceeds a thresholdvalue), and may not include information identifying a value of theaccount parameter.

Further, by way of example, data record 1006 of FIG. 10 may correspondto a connected security system disposed within user 110's home andcapable of communicating with client device 104 over network 120. Asdescribed above, client device 104 may establish a device address forthe security system (e.g., zz:ya:25:8f:44:33). As illustrated in FIG.10, however, user 110 may specify that the security system is ineligibleto receive account status notification information or to present accountstatus indicators to user 110. In certain aspects, user 110'sestablishment of the security system as ineligible for notifications maybe a personal decision that ensures the individuals in user 110's homedo not mistake the presentation of an account status indicator by thesecurity system as an actual alarm.

In some embodiments, and upon receipt of account status notificationinformation from system 140, client device 104 may access data record1000 and may identify one or more connected devices eligible to receivenotification information and present account status indicators to user110. If client device 104 were to identify eligible connected devices,client device 104 may establish communications within the eligibleconnected devices (if such communications were not previouslyestablished), generate device-specific notifications tailored to theaccess and indicator type associated with the eligible connecteddevices, and transmit the generated device-specific notifications to theeligible connected devices directed over network 120 without user 110'sinput or intervention, as described below in reference to FIG. 11.

FIG. 11 illustrates an exemplary process 1100 for present and relayaccount status notifications to eligible connected devices, consistentwith disclosed embodiments. In one embodiment, a client deviceassociated with a user (e.g., client device 104 associated with user110) may be in communication with a system associated with a financialinstitution (e.g., system 140 of business entity 160) and may beconfigured to receive notification information identifying a status ofone or more account parameters of one or more accounts held by user 110.In some aspects, client device 104 may identify one or more identifiableand addressable devices (e.g., connected devices) capable ofcommunicating with client device 104 and presenting visual, tactile,and/or audible indicators of the account status to user 110. Clientdevice 104 may, in some embodiments, transmit notification informationto the connected devices that instructs the connected devices to presentaccount status indicators consistent with capabilities and levels ofaccess assigned to the connected devices by user 110.

In certain aspects, client device 104 may be configured to receiveaccount status notification information from system 140 (e.g., in step1102). As described above, account status notification informationconsistent with the disclosed embodiments may reflect a status of anaccount parameter (e.g., an effective balance) associated with a singleaccount of user 110 (e.g., user 110's checking account), andadditionally or alternatively, statuses of multiple account parametersassociated with one or more of user 110's accounts (e.g., an effectivebalance and remaining available credit associated with a credit cardaccount of user 110, and an actual balance of loyalty points associatedwith a loyalty program account of user 110). In some instances, thereceived account status notification information may include actualvalues of the account parameters and established threshold values (user110's effective checking account balance of $11,500 exceeds thethreshold balance of $10,000), and further, information instructingclient device 104 to generate a particular account status indicatorbased on the actual values and established threshold (e.g., a status barindicator). Further, system 140 may monitor user 110's accounts andgenerate the account status notification information (e.g., based onnotification rules and/or indicator rubrics) using any of the exemplarytechniques described above.

In one aspect, client device 104 may generate and present an accountstatus indicator consistent with the received account statusnotification information. For example, system 140 may generate andtransmit the account status notification information to client device104 in response to user 110's purchase of a particular good or serviceuser a debit card linked to user 110's checking account. In someinstances, the account status notification information may include acurrent effective balance of user 110's checking account (e.g.,$11,500), which may reflect user 110's recent purchase, and a thresholdeffective account balance for user 110's checking account (e.g.,$12,000). The account status notification may also instruct clientdevice 104 to generate a color-coded status bar that conveys a magnitudeof user 110's current effective account balance and that is colored redto convey that the current effective account balance falls below theuser-specified threshold.

In some instances, client device 104 may generate and present thecorresponding account status indicator using any of the exemplarytechniques described above. In other instances, however, client device104 may delegate the generation and/or presentation of the correspondingaccount status indicator to one or more additional devices capable ofcommunicating with client device 104 across network 120.

For instance, and in response to the received account statusnotification information, client device 104 may access profileinformation associated with user 110 to identify the one or moreadditional device (e.g., “connected” devices) capable of communicatingwith client device 104 and deemed eligible by user 110 to receivenotification information and present account status indicators (e.g., instep 1104). As described above, client device 104 may access connecteddevice information stored within a corresponding data structure (e.g.,data structure 1000 of FIG. 10), may determine that a computing devicedisposed within user 110's Mini Cooper™ (e.g., a “connected” MiniCooper™) and a “connected” lighting system disposed within user 110'shome are eligible to receive account status notifications and presentaccount status indicators.

In step 1106, client device 104 may attempt to establish acommunications session with the connected Mini Cooper™ and the connectedlighting system, if suitable communications sessions do not alreadyexist. For example, user 110 may be disposed in the connected MiniCooper™, and client device 104 may be capable of establishingcommunications with the connected Mini Cooper™ across network 120 usingany appropriate communications protocol outlined above. Additionally oralternatively, user 110 may be disposed within or near his or her home,and client device 104 may also be capable of establishing communicationswith the connected lighting system across network 120 using anyappropriate communications protocol outlined above.

Client device 104 may be configured to determine whether anycommunications sessions were successfully established with the eligibleconnected devices (e.g., in step 1108). If client device determines thatno communications sessions with the connected devices could beestablished (e.g., step 1108; NO), then exemplary process 110 iscomplete in step 1110. In certain aspects, when communications cannot besuccessfully established with connected devices, client device 104 maygenerate and present the account status indicator corresponding to thereceived account status notification information using any of theexemplary techniques described above,

If, however, client device 104 were to establish a communicationssession with a corresponding one of the connected devices (e.g., step1108; YES), client device 104 may obtain additional informationidentifying a type of access associated with the corresponding connecteddevice, and further, a type of indicator presentable by thecorresponding connected device (e.g., in step 1112). In certain aspects,client device 104 may generate a device-specific notification for thecorresponding connected device that includes (i) a portion of thereceived account status notification deemed consistent with theidentified access type and (ii) information specifying an account statusindicator consistent with the identified indicator type (e.g., in step1114).

Client device 104 may be configured to transmit the device-specificnotification to the corresponding connected device across network 120using any appropriate communications protocol outlined above (e.g., instep 1116). As described above, client device 104 may be configured totransmit the device-specific notification to the corresponding connecteddevice automatically and without intervention or input from user 110.Upon receipt of the device-specific notification, the correspondingconnected device may be configured to present generate and present thespecified account status indicator to user 110. Upon transmission of thedevice-specific notification to the corresponding connected device,exemplary process 1100 is complete in step 1110.

By way of example, client device 104 may establish a communicationsession with the connected Mini Cooper™ (e.g., in step 1108). Asdescribed above, client device 104 may data associated with theconnected Mini Cooper™ (e.g., data record 1002 of FIG. 10), and maydetermine that user 110 specified an “Authenticated” access type for theconnected Mini Cooper™ (e.g., in step 1112), In certain aspects, user110's establishment of an “Authenticated” access type for the connectedMini Cooper™ implies that account status notification informationprovided to the connected Mini Cooper™ may include actual values of theaccount parameters and established threshold values. Client device 104may also determine in step 1112 that the connected Mini Cooper™ iscapable of generating and presenting status bar indicators, pie chartindicators, background color indicators, picture indicators, symbolindicators, glyph indicators, text-based indicators, and/or auditoryindicators.

In certain aspects, client device 104 may establish that the accountstatus notification information received from system 140 is consistentwith the access type and indicator type established by user 110 for theconnected Mini Cooper™ (e.g., in step 1112). Client device 104 may, forexample, forward the received account status notification information tothe connected Mini Cooper™, which may process the account statusnotification information to generate and present an appropriate accountstatus indicator (e.g., in step 1114). By way of example, and inresponse to the account status notification information, the connectedMini Cooper™ may be configured to generate a color-coded status bar thatconveys a magnitude of user 110's current effective account balance(e.g., $11,500) and that is colored red to convey that the currenteffective account balance falls below the user-specified threshold(e.g., $12,000). The connected Mini Cooper™ may render the generatedcolor-coded status bar for presentation to user 110 through acorresponding display unit (e.g., a touch-screen display or head-updisplay).

Further, in some embodiments, the connected Mini Cooper™ may be capableof presenting additional notifications and indicators to user 110through the corresponding display unit. For example, the connected MiniCooper™ may be configured to generate and present a low-fuel indicatorto user 110 once an amount of remaining fuel falls below a predeterminedlevel (e.g., 10% of capacity). Similarly, the connected Mini Cooper™ maybe configured to display a scheduled service indicator to user 110 at apredetermined point prior to the scheduled service (e.g., when anodometer falls within 3,000 miles of a scheduled 20,000-mile service).

In certain aspects, when the effective balance of user 110's checkingaccount falls below or within predetermined range of the establishedthreshold balance, the connected Mini Cooper™ may increase thepredetermined level of fuel that triggers the low-fuel indicator, andfurther, may present the scheduled service indicator at a mileage closerto that associated with the scheduled service. For example, as thecurrent effective balance of $11,500 falls below the threshold balanceof $12,000, the connected Mini Cooper™ may display the low-fuelindicator when the remaining fuel falls below 20% capacity and/ordisplay the scheduled service indicator when the odometer reading fallswithin 1,000 miles the scheduled 20,000-mile service. In some instances,the additional time before refueling or servicing may allow user 110 tobring the effective account balance of the checking account above theestablished threshold.

In other instances, client device 104 may establish a communicationsession with the connected lighting system (e.g., in step 1108). Asdescribed above, client device 104 may obtain device data associatedwith the connected lighting system (e.g., data record 1004 of FIG. 10),and may determine that user 110 specified an “Indirect” access type forthe connected lighting system (e.g., in step 1112), In certain aspects,user 110's establishment of an “Indirect” access type implies that theaccount status notification information provided to the connectedlighting system may identify a relationship between an account parameterand an established threshold (e.g., whether an effective balance of user110's checking account exceeds a threshold value), but may not includeactual values of the account parameters and established thresholdvalues. Client device 104 may also determine in step 1112 that theconnected lighting system is capable of generating and presenting only abackground color indicator.

In certain aspects, client device 104 may modify the account statusnotification information received from system 140 to generate adevice-specific notification, which may identify that the currenteffective account balance of user 110's checking account falls below theestablish threshold value, and may instruct the connected lightingsystem to glow red for a predetermined period to alert user 110 statusof user 110's checking account (e.g., in step 1114). Client device 104may transmit the device-specific notification to the connected lightingsystem automatically and without input or intervention from user 110,and the connected lighting system may process the device-specificnotification and adjust its display properties to glow red for thepredetermined time period.

The disclosed embodiments may enable client device 104 to receiveaccount status notification information and relay or “push” thatportions of that account status notification information to eligibleconnected devices for presentation to user 110. Although described inreference to a notifications and indicators for a single account, system140 may perform one or more of the exemplary processes described aboveto provide client device 104 with account notification information formultiple accounts (e.g., user 110's checking account and loyalty programaccount), which client device 104 may process and selectively push toone or more eligible devices to presentation in accordance withuser-specified access types and indicator types. For instance, user 110may specify (e.g., via a GUI presented by client device 104) thatvehicle-based eligible devices may receive notification information forany account, while home-based eligible devise (e.g., connected lightingsystems) may receive notification information corresponding to onlyloyalty account.

In aspects, the disclosed embodiments may enable client device 104 torelay or “push” portions of account status notification information toeligible connected devices based on geographic positional information.For instance, client device 104 may identify a particular geographicregion or location associated with an account of user 110 (oralternatively, with user 110) based on notification rules, indicatorrubrics, and/or profile data specified by user 110 using any of thetechniques described above. In one aspects, client device 104 maydetermine its current geographic position (e.g., based GPS information),and may relay or push portions of the account status notificationinformation to eligible devices when the current geographic positionfalls within a threshold distance of the particular geographic region orlocation. In other aspects, client device 104 may receive positionaldata identifying current geographic positions of eligible devices withinenvironment 100 (e.g., when establishing or confirming communicationssessions between client device 104 and the eligible devices).Additionally or alternative, client device 104 may relay or pushportions of the account status notification information to eligibledevices whose current geographic position falls within the thresholddistance of the particular geographic region or location.

Using the exemplary techniques described above, client device 104, inconjunction with system 140, may generate and present indicators thatreflect statuses of account parameters associated with one or more ofaccounts held by user 110. For instance, accounts consistent with thedisclosed embodiments may include financial services accounts (e.g.,checking accounts, savings accounts, brokerage accounts, investmentaccounts, credit card accounts, etc.), student meal plans, gift cards,store credit, wireless communications plans, or any other kind ofaccount capable of maintaining a balance associated with system 140.

The disclosed embodiments are, however, not limited to techniques thatgenerate and present visual, tactile, and audible indicators of accountsheld by user 110. In other embodiments, client device 104 may generateand present visual, tactile, and audible indicators that alert user 110to an upcoming deadline associated with an event. In some aspects, theevent may include a payment associated with an account held by user 110,and the payment may be associated with a corresponding monthly due date(e.g., a monthly due date for a credit card account payment or a duedate for a monthly mortgage payment).

In other aspects, events consistent with the disclosed embodiments mayinclude temporal events having corresponding dates of validity. By wayof example, the event may correspond to an expiration of one or moreloyalty points associated with user 110's loyalty program account. Theaccrued loyalty points may, in some instances, be exchanged by user 110for cash or other rewards that, in some instances, may affect a balanceof an additional account held by user 110. For example, user 110'sloyalty program account may include a balance of 10,000 loyalty points,which may be redeemed by user 110 for purchases at a merchant (e.g., amerchant associated with the loyalty program account), but which mayexpire on a predetermined date. In some aspects, user 110 may redeem atleast a portion of the loyalty points prior to the expiration date forpurchases, which may offset a potential reduction in an effectivebalance of user 110's checking account that would otherwise result fromthe purchase. In other aspects, as described below, at least one of thetemporal events may reflect a consumption of one or more remaining“free” transactions associated with user 110's accounts.

In some embodiments, user 110 may, via client device 104, establishprofile data that specifies one or more events to be tracked by system140, specifies one or more temporal intervals that trigger a generationof an event notification by system 140, and/or associated the eventand/or the event notification with a corresponding indicator presentableby client device 104. In other aspects, user 110 may identify an eventassociated with one or more accounts (e.g., an expiration of loyaltypoints associated with a specified loyalty program account), and system140 may execute software processes that access information associatedwith user 110's loyalty program account (e.g., within stored accountdata 144B, or from a computing system associated with an issuer of theloyalty program account across network 120 through a correspondingapplication programming interface (API)), and determine the deadlineassociated with event based on the accessed account data (e.g., anexpiration date of at least a portion of the loyalty points). Whensystem 140 determines that a current date falls within the establishedtemporal interval of an event deadline, system 140 may generate andtransmit event notification information to client device 104, asdescribed below in reference to FIG. 12.

FIG. 12 illustrates an exemplary process 1200 for generated andproviding event notification information to networked devices,consistent with disclosed embodiments. In one embodiment, a system(e.g., system 140) may be configured to access profile data associatedwith a corresponding user (e.g., user 110), and based on the accessedprofile data, generate and transmit information that, when presented bya client device (e.g., client device 104), notifies user 110 of thedeadline.

In certain aspects, system 140 may access profile data associated withuser 110 (e.g., in step 1202). By way of example, the obtained profiledata may identify one or more events specified by user 110, which may beassociated with corresponding deadlines. In an embodiment, user 110 mayspecify the events and corresponding deadline by providing input to agraphical user interface (GUI) presented by client device 104. Forinstance, user 110 may specify an event corresponding to a mortgagepayment, and may specify a payment due date that reoccurs on the 1^(st)day of each month. In other aspects, user 110 may specify a temporalevent that positively or negatively impacts one or more accounts held byuser 110 (e.g., an expiration of loyalty points redeemable forpurchases, etc.). In additional aspects, user 110 may, through the GUI,link an electronic calendar application to client device 104 (e.g.,through a corresponding API) and automatically populate the user profiledata within events and corresponding deadlines established by theelectronic calendar application. In other instances, the specified eventinformation may enable client device 104 and/or system 140 to determineone or more corresponding deadlines without user input (e.g.,determining an expiration date of loyalty points based on user-specifiedloyalty program account information).

Further, in some instances, the obtained user profile data may identifyone of more temporal intervals that mark dates on which system 140should generate and provide an event notification to client device 104for presentation to user 110. By way of example, user 110 may specify,through the GUI presented by client device 104, that system 140 shouldgenerate event notifications two weeks prior to the payment due date,one week prior to the payment due date, and one day prior to the paymentdue date.

In additional aspects, the obtained user profile data may also associatethe one or more events with corresponding indicator types (e.g., glyphindicators, symbol indicators, image-based indicators, video-basedindicators, audible indicators, etc.) and further, that associate achange to a visible, audible, or tactile characteristic of the indicatortypes with corresponding one or the temporal indicators. In someaspects, user 110's mortgage payment due date may be associated with aglyph indicator corresponding to a flashing green dollar sign presentedtwo weeks prior to the due date, a flashing orange dollar sign presentedone week prior to the due date, and a flashing red dollar sign presentedone day prior to the due date. In other aspects, however, the obtaineduser profile data may specify a different indicator type for eachcombination of event, deadline, and temporal interval. By way ofexample, user 110 may associate a colored visual indicator (e.g., agreen dollar sign) with a notification presented two weeks prior to themortgage payment due date, may associate an animated indicator (e.g.,including visual and audible elements) with a notification presented twoweeks prior to the mortgage payment due date, and may associate anaudible and tactile indicator with a notification presented one dayprior to the mortgage payment due date. In further aspects, theindicator type may correspond to a text-based indicator that includesinformation identifying an initial time period in which the deadlinefalls (e.g., “two weeks”), which system 140 and/or client device 104 maymodify as the deadline approaches (e.g., change “two weeks” to “oneweek,” etc.).

The disclosed embodiments are not limited the above-describedcombinations of indicator types, events, and temporal intervals, and inadditional embodiments the obtained user profile data may associated anyadditional or alternate types of indicators or combinations ofindicators types with events, deadlines, and/or temporal intervals.Furthermore, as described above, user 110 may identify the events,deadlines, corresponding temporal intervals, and associated indicatorsor combinations of indicators through a GUI presented by client device104, which may collect the information input by user 110 as profiledata, and which may transmit the profile data to system 140 for storage(e.g., within stored customer data 144A).

In certain aspects, system 140 may execute software processes that parsethe obtained profile data to extract one or more temporal intervalsspecified by user 110, one or more of the events specified by user 110,and further, one of more of the deadlines associated with the specifiedevents (e.g., in step 1204). By way of example, system 140 may determinethat user 110 specified a deadline of Jan. 1, 2015, for an eventcorresponding to a monthly mortgage payment. Further, in some aspects,system 140 may be configured to identify one or more temporal intervalsassociated with a desired notification. For example, the temporalintervals may specify that user 110 desires a notification of theupcoming deadline two weeks prior to the deadline, one week prior to thedeadline, and one day prior to the deadline. Further, and as describedabove, system 140 may determine a deadline and/or a temporal intervalassociated with a corresponding event based on the user-specifiedprofile date (e.g., system 140 may determine an expiration date ofloyalty points based on loyalty program account information (accountnumbers, etc.) within the obtained profile data).

System 140 may, in some instances, select one of the temporal intervals(e.g., in step 1206) and determine whether a current date falls withinthe temporal interval of the identified deadline (e.g., in step 1208).By way of example, system 140 may initially select the smallest temporalinterval specified by user 110 within the corresponding user profiledata (e.g., one day), and may determine whether the current date (i.e.,December 31^(st)) falls within the one-day temporal interval of theidentified January 1^(st) due date for the mortgage payment.

If system 140 determines that the current date does not fall within theselected temporal interval (e.g., step 1208; NO), system 140 mayidentify an additional event and corresponding deadline from the accessuser profile data (e.g., in step 1210). Exemplary process 1200 may passback to step 1208, and system 140 may execute software processes thatestablish whether the current date falls within the selected temporalinterval of the newly identified deadline.

If, however, system 140 determines that the current date falls withinthe temporal interval of the deadline for the mortgage payment (e.g.,step 1208; YES), system 140 may execute software processes that identifyan indicator type associated with the combination of event, deadline,and temporal interval (e.g., in step 1212). For instance, and asdescribed above, system 140 may identify that user 110 specified that aflashing red dollar sign be presented within a notification that user110's mortgage payment is due on the next calendar day. In some aspects,system 140 may be configured to generate event status notificationinformation (e.g., in step 1214) that identifies the pending deadline ofJanuary 1^(st), identifies the event (e.g., a mortgage payment), andfurther, includes information instructing client device 104 to presentthe specified indicator type to user 110.

System 140 may be configured to transmit the generated event statusnotification information to client device 104 across network 120 usingany of the communications protocols outlined above (e.g., in step 1216).Client device 104 may, in some instances, be configured to process thereceived information, generate the specified event status indicator(e.g., a flashing red dollar sign), and render the event statusindicator for presentation to user 110. In certain aspects, the flashingred indicator, when presented by client device 104, may draw user 110'sattention to client device 104 may enable user 110 to confirm the timelysubmission of the mortgage payment.

In some aspects, and using any of the exemplary techniques describedabove system 140 may determine an impact of the pending deadline onaccount parameters associated with one or more accounts held by user110, and may generate account status notification information thatreflects the determined impact on the one or accounts. In certainembodiments, system 140 may be to incorporate at least a portion of theaccount status notification information within the generated eventstatus notification information (e.g., in step 1214 above). The accountstatus notification information, when processed by client device 104 inconjunction with the event status notification information, may instructclient device 104 to generate and render for presentation a “hybrid”indicator that reflects not only the pending deadline, but also theimpact of that deadline on the one or more accounts held by user 110.

In some aspects, and upon transmission of the event status notificationinformation to client device 104, system 140 may determine whether theaccessed user profile data includes additional events and correspondingdeadlines (e.g., in step 1218). If system 140 determines that additionalevents and due dates requires processing (e.g., step 1218; YES), system140 may execute software processes that identify an additional one ofthe remaining events and corresponding due dates, as described above(e.g., in step 1210).

If, however, system 140 determines that no additional events andcorresponding due dates require analysis under the selected temporalinterval (e.g., step 1218; NO), system 140 may determine in step 1220whether additional temporal intervals within the user profile datarequire analysis. If additional temporal intervals require analysis(e.g., step 1220; YES), system 140 may select one of the additionaltemporal intervals (e.g., in step 1206), and system 140 may pass back tostep 1208, at which time system 140 determines whether identifieddeadlines fall within the newly selected temporal interval. Forinstance, as described above, system 140 may initially select the mostrestrictive time interval specified within the user profile data (e.g.,one day prior to a deadline), and upon processing each specified eventand due date with respect to the most restrictive temporal interval,system 140 may select a less restrictive temporal interval in passingback to step 1206. Alternatively, if no additional temporal intervalsrequire analysis, exemplary process 1200 is complete in step 1222.

Further, in some aspects, system 140's selection of a temporal interval,and the processing of user-established events and deadlines based onthat interval, may be updated at period, regular, and/or user-specifiedintervals. For instance, user 110 may establish, via a GUI presented byclient device 104, and that the exemplary event notification generationand presentation techniques outlined above be updated and reinitiatedevery hour, day, etc. In certain aspects, the user-specified intervalmay define a position of a notification rule, indicator rubric, and/orprofile data.

The disclosed embodiments may enable client device 104 to present agraphical, audible, and/or tactile notification of a current date'sproximity to a deadline for a user-established event. In some aspects,client device 104 and/or system 140 may generate and present the eventstatus notification using any of the exemplary techniques describedabove. For instance, a device component of client device 104 (e.g., anOHMD or heads-up display) may present one or more of the disclosed eventstatus indicators as an AR view that “pops-up” into user 110'sfield-of-view using the techniques described above. Further, in someaspects, client device 104 may perform one or more of the exemplarytechniques described above to identify one or more devices eligible toreceive event notifications, and to transmit or “push” the receive atleast a portion of event notification information to the eligible devicefor presentation. In additional embodiments, client device 104 and/orsystem 140 may determine whether to present the event status indicatorsto user 110 based on geographic locations or regions associated withuser 110, an event, and/or specified within at least one notificationrule or indicator rubric. For instance, client device 104 and/or system140 may perform one or more of the exemplary processes described aboveto identify a geographic location of region associated with the user oran event (e.g., as specified by the user within at least onenotification rule), and to present a corresponding event statusindicator when the user's geographic position falls within a thresholddistance of the geographic location of the user and/or the event.

In other aspects, the disclosed embodiments may enable client device 104and/or system 140 to generate, present, and subsequently modify apresentation of not only event status indicators, but also accountstatus indicators. For instance, client device 104 and/or system 140 maygenerate, present, and modify one or more account status indicatorsassociated with corresponding parameters of accounts held by orassociated with user 110 (and others associated with user 110) using anyof the exemplary techniques described above. In some aspects, using oneor more of the exemplary techniques described above, client device 104and system 140 may generate, present, and or modify one or more eventstatus indicators corresponding user-specified events and deadlines. Incertain embodiments, client device 104 may present one or more of theaccount status indicators to user 110 simultaneously with the eventstatus indicators. For example, client device 104 may present first andsecond account status indicators and event status indicators asconcentric-ring indicators surrounding an object within a field-of-viewof user 110, as described above.

The disclosed embodiments may also enable client device 104 to generateone or more “hybrid” indicators that provide, to user 110, a graphical,audible, or tactile notifications of not only a pending deadline, butalso of an impact of that deadline on one or more of user 110'saccounts. By way of example, system 140 may determine user 110 holds aloyalty program account (e.g., issued by a corresponding merchant)having a balance of 10,000 loyalty points. System 140 may furtherdetermine that 5,000 of the accrued loyalty point balance are scheduledto expire in one week, and additionally, that the expiring 5,000 pointscould be redeemed for a $500 purchase of goods or services from acorresponding merchant. In certain aspects, system 140 may extract theinformation identifying the loyalty program account balance, theexpiring loyalty points, the expiration date, and/or the redemptionvalue from the obtained user profile data, and additionally oralternatively, from a computer system associated with the merchant andaccessible across network 120 through a corresponding API.

In certain aspects, the expiration of the 5,000 loyalty points, andtheir potential redemption for a $500 purchase of goods and/or servicesfrom the merchant may negatively affect an effective balance of user110's checking account (i.e., because in the absence of the redeemedpoints, user 110 would remove $500 from the checking account to purchasethe goods and/or services from the merchant). Using any of the exemplarytechniques outlined above, system 140 may determine that the loss of the5,000 expired loyalty points would correspond to a reduction of $500 inthe effective balance of user 110's checking account, and further, wouldreduce the effective balance below the user-specified threshold.

In some embodiments, system 140 may generate (i) event statusnotification information that indicates the 5,000 loyalty points arescheduled to expire in one month, and (ii) account status notificationinformation that indicates the expiration of the 5,000 would result inan effective balance of user 110's checking account that falls below theuser-specified threshold balance. In certain instances, system 140 maycombine at least a portion of the event and account status notificationinformation to form “hybrid” notification information that instructsclient device 104 to generate a single “hybrid” indicator that reflectnot only the pending expiration of the 5,000 points, but also the impactof the expired 5,000 points on the effective balance of user 110'schecking account. System 140 may, for example, determine visual,audible, and/or tactile characteristics of the hybrid indicator usingany of the exemplary techniques outlined above (e.g., based portions ofnotification rules, indicator rubrics, and/or user profile data), andsystem 140 may transmit the hybrid notification information to clientdevice 103 across network 120.

In certain aspects, client device 104 may receive the hybridnotification information, and using any of the exemplary techniquesoutlined above, generate and present the hybrid indicator that reflectsthe pending expiration of the 5,000 points and the impact of the expiredpoints on user 110's effective checking account balance. For example,and based on the hybrid notification information, client device 104 maygenerate and present a glyph indicator that includes a textualdescription of the effective balance of user 110's checking account andthe impact (e.g., the reduction) on the effective balance that wouldresult from the expiration of the 5,000 points, and further is coloredyellow to indicate to user 110 that the 5,000 points expire in onemonth. In other instances, as the expiration date nears, system 140 mayinstruct client device 104 to modify a visual, tactile, and/or audiblecharacteristic of the presented hybrid indicator to alert the user ofthe pending expiration. For example, client 140 may color the hybridindicator red to indicate that the 5,000 points expire in one week, andadditionally or alternatively, the hybrid indicator may flash to alertthe user to the pending expiration.

In other embodiments, system 140 may be configured to separatelytransmit at least a portion of the generated account status notificationinformation and event status notification information to client device104. Using any of the exemplary techniques described above, clientdevice 104 may generate and present an account status indicator thatreflects the impact of the expired loyalty points on user 110'seffective checking account balance, and further, an event statusindicator reflecting the pending expiration of the loyalty points.Client device 104 may be configured to present the account statusindicator proximate to the event status indicator, as surrounding theevent status indicator, or in accordance with any of the exemplaryconfigurations outlined and specified in corresponding portions ofnotification rules, account rubrics, and/or user profile data.

The disclosed embodiments may enable client device 104 to present one ormore indicators that reflect not only a deadline associated with apending event, but also an impact of that deadline (or an actionassociated with the deadline) on one or more accounts held by user 110.In certain aspects, the proximity of the deadline to the current datemay provide context that enables user 110 to determine an importance ofthe impact on the one or more accounts. For example, user 110 mayelectronically pay each month's bills on the 15^(th) day, and clientdevice 104 may present a hybrid indicator to user 110 that indicatesuser 110's effective checking account balance falls below theuser-specified threshold, and further, that is colored green to indicateuser 110's checking account will receive funds corresponding tobi-monthly wages in two days. Additionally or alternatively, the hybridindicator may be colored green to indicate that user 110's nextscheduled bill payment falls after the scheduled receipt of wages. Inother instances, client device 104 may be configured to presented anaccount status indicator colored red to indicate that the effectivebalance of user 110's checking account falls below the user-specifiedthreshold balance, while simultaneously presenting an event statusindicator colored green to indicate that user 110's checking account isscheduled receive wages during the next twenty-four hours. Based on thepresented indicators, user 110 may understand that his or checkingbalance falls below the threshold value, but may perceive little risk tothe reduced balance due to the pending pay date and/or distant due date.

Further, as noted above, account parameters consistent with thedisclosed embodiments may reflect a current usage and/or a remainingavailable usage of the one or more accounts. For example, user 110 mayhold a debit card issued by the financial institution, which may providea predetermined number of “free” transactions involving the debit cardat participating ATMs (e.g., a predetermined number of withdrawaltransactions without accruing fees). In certain aspects, the accountparameter information may identify a number of transactions involvingthe debit card at the participating ATMs, a number of remaining freetransactions, and any additional or alternate parameters describe user110's current or remaining available usage. Further, in some aspects,the remaining free transactions may expire after a certain time period,and the account parameter information consistent with the disclosedembodiments may also identify the expiration date of the remainingtransactions.

In some instances, system 140 may be configured to determine that user110's checking account has fifteen remaining “free” transactions, andthat once consumed, user 110's checking account will be charged a fixedmonthly fee (e.g., based on user-specified profile information). System140 may generate status notification that identifies the remaining freetransactions and the fixed monthly fee, and may transmit the statusinformation to client device 104. In certain aspects, client device 104may generate and present to user 110 an indicator that identifies thenumber of remaining free transactions (e.g., as an “event”), andfurther, that modifies a visual, audible, or tactile characteristic ofthe indicator to reflect the user's consumption of the free transactions(e.g., the approach to the “deadline” of zero free transactions). Incertain aspects, the indicator may be colored green if greater than tenfree transactions remain, glow yellow if between five and ten freetransactions remain, and further, may glow red and/or flash when fewerthan five free transactions remain. Further, in some aspects, thereceived status information may include an expiration date of theremaining free transactions, and the generated and presented indicatormay reflect the expiration date, and the time until the expiration date,using any of the exemplary techniques outlined above.

Other embodiments will be apparent to those skilled in the art fromconsideration of the specification and practice of the embodimentsdisclosed herein. It is intended that the specification and examples beconsidered as exemplary only, with a true scope and spirit of thedisclosed embodiments being indicated by the following claims.

What is claimed is:
 1. An apparatus, comprising: a storage device; andat least one processor coupled to the storage device, the storage devicestoring software instructions for controlling the at least one processorwhen executed by the at least one processor, the at least one processorbeing operative with the software instructions and being configured to:obtain information identifying an event and corresponding deadlinespecified by a user, the information linking the event and deadline to aplurality of temporal notification intervals, the temporal notificationintervals being linked to corresponding indicator types; determinewhether a current date falls within a first time period prior to thedeadline, the first time period being established by a first one of thetemporal notification intervals; when the current date is determined tofall within the first time period, identify a first indicator typeassociated with the first temporal notification interval; generate firstevent notification information for the identified event based on atleast one notification rule and a status of the identified event, theidentified event status being indicative of the disposition of thecurrent date within the first time period; and generate account statusnotification information for an account of the user based on the atleast one notification rule and information associated with the useraccount, the account status information being indicative of an impact ofthe event on an account parameter associated with the user account; andprovide the first event notification information and the account statusnotification information to a device associated with the user; whereinthe first notification information and the account status notificationinformation instruct the user device to generate and present, to theuser, (i) a first event status indicator reflective of the identifiedevent status, and (ii) an account status indicator reflecting the impactof the event on the user account parameter.
 2. The apparatus of claim 1,wherein at least one of a visual, audible, or tactile characteristic ofthe first event status indicator is consistent with the at least onenotification rule and the first indicator type.
 3. The apparatus ofclaim 1, wherein the at least one processor is further configured toobtain information identifying a geographic position of the user device.4. The apparatus of claim 3, wherein: the notification rule comprisesindication associating a geographic region with the user; and the atleast one processor is further configured to: determine whether thegeographic position of the user device falls within a threshold distanceof the associated geographic region; and when the geographic position ofthe user device is determined to fall within the threshold distance,provide the first notification information to the user device.
 5. Theapparatus of claim 1, wherein the first indicator type comprises atleast one of a graphical status bar, a dynamic graphical icon, or aglyph.
 6. The apparatus of claim 1, wherein the obtained informationcorresponds to profile information specified by the user, theuser-specified profile information identifying at least one of thetemporal notification intervals and an indicator type corresponding theat least one user-specified temporal notification interval.
 7. Theapparatus of claim 6, wherein: the user-specified profile informationassociates an animated indicator type with the at least oneuser-specified temporal notification interval; and the animatedindicator type is associated with at least one of an element of digitalimage content or digital video content specified by the user.
 8. Theapparatus of claim 1, wherein the at least one processor is furtherconfigured to: identify a second one of the temporal notificationintervals, when the current date is determined not to fall within thefirst time period; and determine whether the current date falls within asecond time period prior the deadline, the second time period beingestablished by the second temporal notification interface, and thesecond time period exceeding the first time period.
 9. The apparatus ofclaim 8, wherein the at least one processor is further configured to:when the current date is determined to fall within the establishedsecond time period, identifying a second indicator type associated withthe second temporal notification interval; generate second notificationinformation based on at least one notification rule and informationindicative of the disposition of the current date within the second timeperiod; provide the second notification information to the user deviceassociated with the user, wherein the second notification informationinstructs the user device to generate and present, to the user, a secondevent status indicator in accordance with the at least one notificationrule and the second indicator type.
 10. The apparatus of claim 1,wherein the at least one processor is further configured to: when thecurrent date is determined to fall within the first time period,identify a third one of the temporal notification intervals; anddetermine whether the current date falls within a third time periodprior the deadline, the third time period being established based on thethird temporal notification interval, and the first time periodexceeding the third time period.
 11. The apparatus of claim 10, whereinthe at least one processor is further configured to identify the thirdtemporal notification interval at a user-specified time after thedetermination of whether current date fell within the first time period.12. The apparatus of claim 10, wherein the at least one processor isfurther configured to: when the current date is determined to fallwithin the third time period, generate modified notification informationfor the identified event based on the disposition of the current datewithin the third time period; and provide the first notificationinformation to a device associated with the user, wherein the thirdnotification information instructs the user device to modify at least atleast one of a visual, audible, or tactile characteristic of thepresented first event status indicator in accordance with a thirdindictor type associated with the third temporal notification interval.13. The apparatus of claim 1, wherein the at least one processor isfurther configured to obtain at least one of the event or thecorresponding deadline from an application program executed by the userdevice, the at least one event or corresponding deadline being obtainedthrough a programmatic interface associated with the applicationprogram.
 14. The apparatus of claim 1, wherein: the event corresponds toan expiration of at least one loyalty point associated with a loyaltyprogram account held by the user; the deadline corresponds to anexpiration date of the at least one loyalty point; the account parametercorresponds to an effective account balance of a checking account heldby the user; and the expiration of the at least one loyalty pointresults in a reduction of the effective account balance by apredetermined amount.
 15. The apparatus of claim 1, wherein the accountparameter includes at least one of: a balance of a corresponding one ofthe user account; a potential account balance that reflects whether theuser account can accommodate a potential purchase of a product orservice from a merchant; a predictive account parameter that reflects apredicted balance of the user account based on at least one priorpayment; a balance of a loyalty program associated with a correspondingone of the first or second accounts; or a potential balance of theloyalty program that reflects a potential purchase of the product orservice from the merchant.
 16. A computer-implemented method,comprising: obtaining, by at least one processor, informationidentifying an event and corresponding deadline specified by a user, theinformation linking the event and deadline to a plurality of temporalnotification intervals, the temporal notification intervals being linkedto corresponding indicator types; determining, by the least oneprocessor, whether a current date falls within a first time period priorto the deadline, the first time period being established by a first oneof the temporal notification intervals; when the current date isdetermined to fall within the first time period, identifying, by theleast one processor, a first indicator type associated with the firsttemporal notification interval; generating, by the least one processor,first notification information for the identified event based on atleast one notification rule and a status of the identified event, theidentified event status being indicative of the disposition of thecurrent date within the first time period; generating, by the at leastone processor, account status notification information for an account ofthe user based on the at least one notification rule and informationassociated with the user account, the account status information beingindicative of an impact of the event on an account parameter associatedwith the user account; and providing, by the least one processor, thefirst notification information and the account status notificationinformation to a device associated with the user, wherein the firstnotification information and the account status notification informationinstruct the user device to generate and present, to the user, (i) afirst event status indicator reflective of the identified event status,and (ii) an account status indicator reflecting the impact of the eventon the user account parameter, the first event status indicator havingat least one of a visual, audible, or tactile characteristic consistentwith the at least one notification rule and the first indicator type.17. The method of claim 16, wherein the obtained information correspondsto profile information specified by the user, the user-specified profileinformation identifying at least one of the temporal notificationintervals and an indicator type corresponding the at least oneuser-specified temporal notification interval.
 18. A device, comprising:a storage device; and at least one processor coupled to the storagedevice, the storage device storing software instructions for controllingthe at least one processor when executed by the at least one processor,the at least one processor being operative with the softwareinstructions and being configured to: receive first status notificationinformation for at least one event and an account status indicatorreflecting the impact of the event on an account parameter of at leastone user account, the event being associated with a correspondingdeadline, and the received status notification information reflecting adisposition of a current date within a first time period prior to thedeadline, the first time period being established by the first temporalinterval, and the first temporal interval being associated with a firstindicator type; based on the received status notification information,generate (i) an event status indicator in accordance with the firstindicator type and (ii) an account status indicator in accordance withat least one notification rule, the generated event status indicatorreflecting the disposition of the current date within the first timeperiod, and the generated account status indicator reflecting the impactof the event on the at least one user account parameter; and present, tothe user, the event status indicator and the account status indicatorwithout receiving input from the user, at least one a visual, audible,or tactile characteristic of the presented event status indicator beingconsistent with first indicator type.
 19. The device of claim 18,wherein the at least one processor is further configured to present aleast one of (i) a graphical representation of the event statusindicator through a corresponding interface of the user device or (ii)an audible representation of at least one of the event status indicatorthrough a speaker included in the device.
 20. The device of claim 19,wherein the graphical representation comprises at least one of a statusbar, a dynamic graphical icon, or a glyph.
 21. The device of claim 18,wherein the at least one processor is further configured to: generate agraphical configuration interface based on configuration informationreceived by the device; and present the graphical configurationinterface to the user via a device component, the configurationinterface allowing the user to identify at least one of the event, thedeadline, or the first temporal interval.
 22. The device of claim 18,wherein the at least one processor is further configured to obtaingeographic information identifying a geographic position of the userdevice.
 23. The device of claim 22, wherein; the notification rulecomprises indication associating a geographic region with the user; andthe at least one processor is further configured to: determine whetherthe geographic position of the user device falls within a thresholddistance of the associated geographic region; and when the geographicposition of the user device is determined to fall within the thresholddistance, present the event status indicator to the user.
 24. The deviceof claim 18, wherein the at least one processor is further configuredto: obtain information identifying a device eligible to access thestatus notification information in accordance with a data restrictionspecified by the user; identify at least a portion of the statusnotification information for transmission to the eligible device, theidentified portion being consistent with the data restriction; andprovide the identified portion of the status notification information tothe eligible device without receiving input from the user, the statusnotification information portion instructing the eligible device topresent at least one of a visual, audible, or tactile indicator of theevent status.
 25. The device of claim 18, wherein the at least oneprocessor is further configured to: obtain image data representative ofa portion of an environment visible to the user, the obtained image datarepresenting a digital image of a portion of an object visible to theuser within the environment; and present, via a display component, thegenerated event status indicator within a field-of-view of the userwithout receiving input from the user, the presented event statusindicator being visible to the user within the environment, andmodifying a visual appearance of the object within the environment toreflect the disposition of the current date within the first temporalinterval.
 26. The device of claim 18, wherein the at least one processoris further configured to: receive second notification informationassociated with the identified event, the second notificationinformation reflecting a disposition of the current date within a secondtime period established by a second temporal interval; modify at leastone of a visual, audible, or tactile characteristic of the presentedevent status notification to reflect the disposition of the current timewithin the second time period, the modification being consistent withthe at least one notification rule and a second indicator typeassociated with the second temporal interval; and present the modifiedevent status indicator to the user.
 27. The device of claim 26, wherein:the presented event status notification includes a textualrepresentation of the first time period; and the at least one processoris further configured to modify the textual representation to identifythe second time period.
 28. The device of claim 18, wherein the at leastone processor is further configured to: the event corresponds to anexpiration of at least one loyalty point associated with a loyaltyprogram account held by the user; the deadline corresponds to anexpiration date of the at least one loyalty point; the account parametercorresponds to an effective account balance of a checking account heldby the user; and the expiration of the at least one loyalty pointresults in a reduction of the effective account balance by apredetermined amount.
 29. The device of claim 28, wherein the at leastone processor is further configured to present the at least one of thefirst or second status indicators to the user simultaneously with theevent status indicator via the device component.
 30. The device of claim28, wherein at least one of the first or second account parametersincludes at least one of: a balance of a corresponding one of the firstand second accounts; a potential account balance that reflects whether acorresponding one of the first and second account balances canaccommodate a potential purchase of a product or service from amerchant; a predictive account parameter that reflects a predictedbalance of a corresponding one of the first and second accounts based onat least one prior payment; a balance of a loyalty program associatedwith a corresponding one of the first or second accounts; or a potentialbalance of the loyalty program that reflects a potential purchase of theproduct or service from the merchant.